Comment 0 for bug 1494851

When crypttab specifies a key-file for the container of the root file-system but there is no keyscript= option no cryptsetup support is installed in the initrd.img.

Currently the cryptroot initramfs hook script knows its a problem and will report:

cryptsetup: WARNING: target LUKS_OS uses a key file, skipped

This is BAD behaviour that renders the root file-system container inaccessible at boot time.

Regardless of a key-script being available cryptsetup support should be installed into the initrd.img to enable the user to take manual steps to unlock the container. The hook script has no knowledge about pass phrases that might be set in other LUKS slots that are available to the user.

The attached patch modifies the behaviour to include cryptsetup in the initrd.img and modify the warning to the user.

cryptsetup: WARNING: target LUKS_OS uses a key file, but no keyscript is set. Please ensure there is also a typed pass-phrase set.