Red Hat Bugzilla – Bug 309531
add cryptsetup(-luks) and crypto kernel modules to rescue cd
Last modified: 2013-01-09 23:26:22 EST
Description of problem:
The rescue cd does not contain cryptsetup-luks, but this would be useful in
cases one has an encrypted filesystem on ones harddisk and needs to access data
Imho these kernel modules are needed, to make cryptsetup-luks work:
Optionally also these:
And this kernel module seems to be useful for a rescue cd, too:
It would be helpful, if these modules were also on the normal install image, btw.
Dave - if you haven't already taken care of all of this as part of your
encrypted filesystem support, this may be something for you to look into.
I was just able to use rescue mode on a system with encryption over raid. I have
the raid arrays mounted and they seem OK. (I haven't done the actual rescuing
yet, but that should be possible.) I do have a nit about how it works though.
I get asked to enter a password for each partition as well as each array. I
think for software raid partitions, besides looking for a luks signature, it
should also look for the raid array info. If it finds both, then the encryption
should be over raid and it shouldn't try to use it for that partition. If it
finds luks, but no raid info, then it should prompt for a password because it
might be raid over encrypted partitions.
To get it to work I hit cancel as each partion was asked about and then gave the
password (there was just one for all of the encrypted arrays) for the first
array and checked global password and then wasn't prompted for the the other
two. All of them (/, /home and /play) were mounted under /mnt/sysimage.
Bruno -- can you file something separate on the RAID case (as yeah, it
definitely seems like that needs to be fixed). But it looks like the basic bits
here are all set