On Sun, Oct 29, 2023 at 03:10:18PM +0100, Nicolas Melot wrote:
> This is a repost of the same bug report I submitted to Ubuntu maintainers on
> https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2031499 and that
> seems to have been left as is. I am now hitting the same issue on Debian
> Bookworm.

I have exactly the same problem with a setup where another crypt device
needs to be unlocked BEFORE the root file system because the other crypt
device holds part of the key.

And I came to the same solution independently.

Hence, this is not a totally exotic use case at least, since two users
came even to the same solution.

After taking a step back I also find the solution quite elegant: It
preserves the order of the crypt devices as given by the local admin, it
just adds the devices that the local admin didn't specify while the
system knows a device is needed. The admin has the option of taking
the complete crypttab in their own hands transparently.

Please consider implementing this.

Greetings
Marc

Reply via email to