http://bugzilla.novell.com/show_bug.cgi?id=577127 http://bugzilla.novell.com/show_bug.cgi?id=577127#c Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell@novell.com AssignedTo|aschnell@novell.com |juhliarik@novell.com -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=577127 http://bugzilla.novell.com/show_bug.cgi?id=577127#c2 --- Comment #2 from Jeff Mahoney 2010-02-09 16:27:43 UTC --- Created an attachment (id=341537) --> (http://bugzilla.novell.com/attachment.cgi?id=341537) y2logs Logs as requested. The system has been up since the installation, so there may be a lot more info in there than needed. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=577127 http://bugzilla.novell.com/show_bug.cgi?id=577127#c4 Thomas Fehr changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|aschnell@novell.com |juhliarik@novell.com --- Comment #4 from Thomas Fehr 2010-02-10 11:39:22 UTC --- So far the name of the name of the dm device used for encrypted access to the original device was not available in YCP code. I changed this now. For devices using dm encryption there is now an additional entry "crypt_device" in map that contains the name of the dm device used for encryption. Here is an example for encryption used for /dev/sda5: "crypt_device" : "/dev/mapper/cr_name", "detected_fs" : `swap, "device" : "/dev/sdc5", "enc_type" : `luks, "name" : "sdc5", "nr" : 5, So bootloader should use the name provided in key "crypt_device" instead of "device" when "enc_type" is `luks. This extension is available with libstorage-2.19.9 and yast2-storage-2.19.6. Both new packages have just been submitted to Factory. Reassigning to Jozef so he can do the necessary changes in bootloader. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=577127 http://bugzilla.novell.com/show_bug.cgi?id=577127#c6 --- Comment #6 from Thomas Fehr 2010-02-10 12:27:49 UTC --- To my knowledge, there is no FATE entry for that. The changes were quite easy to do and might also help other areas in YaST2 having to deal with encrypted devices and can hardly break any existing code. It is totally up to you to decide if and when the functionality of resuming from an encrypted device should be added to bootloader. What I wanted to avoid is that someone needing the information about dm encrypted devices needs to fiddle around with "dmsetup table" itself, while the needed information is easily available inside libstorage anyway. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=577127 http://bugzilla.novell.com/show_bug.cgi?id=577127#c8 Thomas Fehr changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|fehr@novell.com | --- Comment #8 from Thomas Fehr 2010-02-10 14:39:39 UTC --- Currently, we do not allow to set encryption for root filesystem. So it is not possible to have "crypt_device" set for root filesystem. You may have an encrypted root via encryption of the whole LVM volume group, but this does not need any changes in bootloader. The entry "crypt_device" is not special for swap, every encrypted device will have a key named "crypt_device". Of course the problem here could also be fixed when initrd would be modified to detect and set up an encrypted swap during resume by looking at files fstab and crypttab. . No idea which is easier to do. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=577127 http://bugzilla.novell.com/show_bug.cgi?id=577127#c10 --- Comment #10 from Jeff Mahoney 2010-02-19 17:22:14 UTC --- Still present in M2 (yast2-bootloader 2.19.1). 2.19.4 doesn't appear to be in Factory yet. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.