Excerpts from jaivuk's message of Sat Mar 19 15:02:09 +0100 2011: > However when I added rd.luks.key=/mykey:abcd-1234 into the grub > (Instead of abcd-1234 I use real UUID of my key) the boot fails and I > end up in the dracut shell. > > Here is how my updated kernel parameters look like: > > kernel /vmlinuz-2.6.35.11-83.fc14.i686 ro root=/dev/mapper/vg2-lv_root > rd.luks.uuid=luks-6508ce25-91d1-469a-9423-7b10ef00754e > rd.luks.uuid=luks-73608094-4b4d-48bf-99a6-0493aeb7498d > rd.luks.uuid=luks-9d1124c6-22fe-4572-984b-175c0e307a1f > rd.luks.uuid=luks-eac11ed2-4136-4f73-bda7-1af1c09fe644 > rd.md.uuid=eb005502:33822bc2:b956ad0a:be45f8e0 > rd.md.uuid=9ce2b0c0:ed400210:451f5dab:694b56f7 > rd.md.uuid=5e644250:1dda1a02:9365481e:4e0aee0a > rd.md.uuid=2e0eedaf:41d79b6b:0bed1099:5adc22ef rd.lvm.lv=vg2/lv_root > rd.lvm.lv=vg2/lv_swap rd.dm=0 rd.luks.key=/mykey:abcd-1234 UUID should be prefixed with UUID=, so it should be: rd.luks.key=/mykey:UUID=abcd-1234 because you can specify labels there, too: rd.luks.key=/mykey:LABEL=keys > The change in dracut seem to be quite turbulent and I hope it will > settle a bit. It make take me a while to create patch for dracut 008 > and then I can realize you are elsewhere with dracut 009... Options format is settled with 008. We're not planning any further changes. > dracut.kernel man page confuses me as well: > "If luksdev is given, the specified key will only be applied for that > LUKS device. Possible values are the same as for keydev. Unless you > have several LUKS devices, you don't have to specify this parameter." > > I have several luks devices, but one key only. Does it mean I have to > list them all manually for the key again? I meant that if you have several luks devices with different keys, you can specify which key is for which device to avoid unnecessary decryption of other devices. > So I have to ask you - what logic is used to mount luks partitions > with the key on external device in dracut 008? > (When I modified dracut 005 I had to add delay before USB was checked, > in dracut 008 USB is checked in the loop but if it fails, it does not > ask for password, but ends in shell.) In Dracut 008 devices are probed for key file asynchronously with udev rules. If device eventually appears, it's probed for key. If key is found, it's added to the list of possibles keys to try. > I have this idea how it can be done (when external key is specified) > I suggest to replace once instance of cryptsetup luksOpen command > which waits for password and blocks boot proccess > with two parallel instances which will try to unlock the same luks device: > - first instance will ask user for password - in the same way it is > done now - cryptsetup luksOpen, > - second intance will: > a) monitor keydev in the loop with sleep. Once keydev is mounted and > the key is found, it will try to unlock luks partition with that key > and when this is successful, > b) Then it will kill the crytpsetup process waiting in the first > instance, first instance will then recheck luks device was > successfully mounted and boot will continue. > > In my view this can be implemented without any changes in the > cryptsetup tools. Another option to consider is to try to mount luks > device based on event comming from udev (once key is attached) - and > then perform point b) - what do you think? As said above, it's based on udev since 008. > In this way once user is asked for password he/she can either enter it > manually or insert the key. You suggest that for every luks device Dracut should stop and let the user decide to choose between key or password? -- Amadeusz ÅoÅnowski PGP key fpr: C700 CEDE 0C18 212E 49DA 4653 F013 4531 E1DB FAB5
Attachment:
signature.asc
Description: PGP signature
