Bug 464895 - Support for global pass phrase for encrypted block devices
Summary: Support for global pass phrase for encrypted block devices
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: initscripts
Version: 5.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: initscripts Maintenance Team
QA Contact: BaseOS QE
URL:
Whiteboard:
Depends On:
Blocks: RHEL5u3_relnotes 549609
TreeView+ depends on / blocked
 
Reported: 2008-10-01 08:00 UTC by Alexander Todorov
Modified: 2009-12-22 03:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
On systems with more than two encrypted block devices, anaconda has a option to provide a global passphrase. The init scripts, however, do not support this feature. When booting the system, entering each individual passphrase for all encrypted devices will be required.
Clone Of:
: 549609 (view as bug list)
Environment:
Last Closed: 2008-10-02 14:04:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Alexander Todorov 2008-10-01 08:00:58 UTC
Description of problem:
Anaconda supports global pass phrase for block device encryption. It should be supported by initscripts as well

Version-Release number of selected component (if applicable):
initscripts-8.45.20-1

How reproducible:
Always

Steps to Reproduce:
1. Install a system with 2 or more encrypted block devices. By default anaconda will usea global pass phrase
2. Boot into the new system
  
Actual results:
Upon boot the user is required to enter the same pass phrase for every single encrypted device

Setting up disk encryption: /dev/sda2
Enter LUKS passphrase: 
Setting up disk encryption: /dev/sdb1
Enter LUKS passphrase:


Expected results:
The user should enter the pass phrase once and it should be used to decrypt all other device. In case that fails (i.e. some device is encrypted with other pass phrase) then ask again.

Additional info:
This is fixed in Rawhide in bug #459191

Comment 1 Bill Nottingham 2008-10-01 16:14:19 UTC
plymouth is not going in RHEL 5 any time soon, and this really can't be fixed without it.

Comment 2 Alexander Todorov 2008-10-02 07:21:20 UTC
I'm not asking to port plymouth to RHEL 5 but to instrument some logic in the init script responsible for decrypting partitions. The way I see it is:

1) Ask for passphrase
2) Store the pass phrase into some variable in the script
3) Try to unlock the partition, if fails ask again
4) Repeat 1-3 /optionally accumulate entered passwords and try with all/

Comment 3 Bill Nottingham 2008-10-02 14:04:23 UTC
That would involve writing entirely separate widgetry just to ask for the password and keep it around, as we're certainly not going to be asking for passphrases in shell code. It's not worth it to do a one-off solution like that for RHEL 5.

Comment 5 Alexander Todorov 2008-10-02 14:35:44 UTC
Release note added. If any revisions are required, please set the 
"requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

New Contents:
Although Anaconda provides the ability to use a global pass phrase for all encrypted block devices this is not supported from the init process. The user will have to manually enter the pass phrase for every encrypted device when booting the system.

Comment 6 Ryan Lerch 2008-10-06 02:48:46 UTC
Release note updated. If any revisions are required, please set the 
"requires_release_notes"  flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

Diffed Contents:
@@ -1 +1 @@
-Although Anaconda provides the ability to use a global pass phrase for all encrypted block devices this is not supported from the init process. The user will have to manually enter the pass phrase for every encrypted device when booting the system.+On systems with more than two encrypted block devices, anaconda has a option to provide a global passphrase. The init scripts, however, do not support this feature. When booting the system, entering each individual passphrase for all encrypted devices will be required.


Note You need to log in before you can comment on or make changes to this bug.