Bug 446930

Summary:	kickstart encrypted filesystem prompt for passphrase doesn't work
Product:	[Fedora] Fedora	Reporter:	Chris Schanzle <bugzilla>
Component:	anaconda	Assignee:	David Lehman <dlehman>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	9	CC:	phil
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-02-16 20:32:14 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Chris Schanzle 2008-05-16 17:13:37 UTC

Kickstart will not prompt for a passphrase when the actual passphrase is omitted
as documented in kickstart-docs.txt. I'm using options "--encrypted
--passphrase=".  Result is unencrypted devices.  Happens with both "text" and
graphical installs.  Actually giving a password using --passphrase=password
works, but is insecure to embed in the kickstart file.

100% reproducible.

I'm hopeful an anaconda patch to load during kickstart will appear so we don't
have to wait for F10.

Comment 1 Philip Mather 2008-06-04 11:45:39 UTC

Bump, vote or whatever.
   I really need this or even better to be able to specify a location to write a
key to such as "--key-file=/dev/sdc1/disk.key" would be unbelievably handy. I
can then prompt the user either post-install or at first-boot to set a
pass-phrase as an alternative or then and a company wide recovery key somehow.

Comment 2 David Lehman 2008-08-14 19:51:53 UTC

Fix will be in anaconda-11.4.1.29-1 (rawhide).