Description of problem: I multiple crypt devices in /etc/crypttab, eg: home /dev/vg_local/home_crypt var /dev/vg_local/var_crypt At boot time, I am prompted for 2 passwords. However, the password prompt does not tell me which device's password I am being prompted for. It turns out that it's the order in which they're listed in /etc/crypttab, but you just have to remember that. Version-Release number of selected component (if applicable): initscripts-8.45.19.EL-1.i386
This message comes from cryptsetup-luks.
*** This bug has been marked as a duplicate of 433406 ***
Whoops, cross-product. Sorry about that.
Fixed in cryptsetup-luks-1.0.3-5.el5.
I have / and swap on LVs which are encrypted. With 5.3 cryptsetup-luks and latest one from 5.4 I get: Setting up disk encryption for: /dev/mapper/VolGroup00-LogVol00 Enter LUKS passphrase: Setting up disk encryption for: /dev/mapper/VolGroup00-LogVol01 Enter LUKS passphrase: This looks like verified but it's already in 5.3. If I read the patch from comment #4 correctly it should be: Enter LUKS passphrase for /dev/mapper/VolGroup00-LogVol00: Milan, can you clarify what was the fix? Thanks
The message "Setting up disk encryption for:" is printed by initscripts/initrd an not cryptsetup itself. cryptsetup now should print prints "Enter LUKS passphrase for /dev/mapper/VolGroup00-LogVol00". (uu can try run it manuallly on some LUKS device) But if you have encrypted root, you have to update initrd after uprading cryptsetup otherwise it use old version included in initrd.
I have / and swap encrypted. with cryptsetup-luks-1.0.3-5.el5 and latest RHEL5.4 tree I get: Setting up disk encryption for: /dev/mapper/VolGroup00-LogVol00 Enter LUKS passphrase for /dev/mapper/VolGroup00-LogVol00: Setting up disk encryption for: /dev/mapper/VolGroup00-LogVol01 Enter LUKS passphrase for /dev/mapper/VolGroup00-LogVol01: moving to verified.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-1349.html