On Mon, Apr 03, 2017 at 11:21:14PM +0000, Rusty Bird wrote: > Did you try the "rd.luks.key=LUKSUUID=KEYFILE" workaround? IIRC, this > shouldn't trigger the buggy if branch.
I haven't tried that one, although I did build a patched version of systemd v227 with the fix applied and found another problem -- it seem to only apply the keyfile to the root device and prompts for a password for the other partitions. So as a workaround I'm generating a /etc/cryptab that specifies /secret.key for every paritition and inserting those two files into the initrd at boot time. This works, although the rebuilding the cpio is slow. What controls the generate of /etc/crypttab in the initrd during a system upgrade? Would it be possible to have it create the correct entries for all the partitions instead? -- Trammell -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/20170404001338.GG30182%40chishio.swcp.com. For more options, visit https://groups.google.com/d/optout.
