[systemd-devel] cryptsetup: disk unlocking order

[Lennart Poettering]

On Sun, 28.10.12 15:33, Martin Blumenstingl (martin.blumenstingl at googlemail.com) wrote:

> Hi,
> 
> I switched to systemd yesterday as I was curious if/how it would work
> out for me.
> There is one really annoying thing so far:
> 
> I have 3 hard disks listed in /etc/crypttab.
> I have to enter a password for each one at boot time.
> Three disks means three passwords (strong, 15+ characters).
> 
> It turns out that the order in which I'm asked for the passwords at startup
> is completely random.
> At first I was asked in an alphabetical order (/mnt/a, /mnt/b, /mnt/c).
> On the next reboot it used the order in which the disks are listed in
> /etc/crypttab.
> The reboot after that had a completely different order.
> 
> Is there any fix for this behavior?
> I'm using systemd 195 on Arch Linux.

If Plymouth is used plymouth can do the necessary caching.

That said it is actually my intention to use the kernel keyring for
this, so that this wokrs independently of Plymouth and requires no
further userspace infrastructure.

Lennart

-- 
Lennart Poettering - Red Hat, Inc.