<teg <at> jklm.no> writes:
From: Tom Gundersen <teg <at> jklm.no>
We detect if the old syntax is used, and if so print a warning and use the old parsing code. Otherwise, we pass everything on to systemd-cryptsetup. Similarly to what was done with the network syntax, we intend to keep the legacy stuff working for a long time.
See crypttab(5) for the new syntax[0].
The main reason for this change, is to be closer to what other distros do. The systemd syntax is based on Debian's format, and is essentially what is being used by at least Debian, Ubuntu, Fedora and Suse. Such widespread use means that it will be better documented in non-Arch-specific documentation, and is more likely to see integration with third-party tools. It is also surely appreciated by admins who use more than one distro, that they don't have to know more than one config format for these sorts of basic things.
Hi, there is other problem too: systemd-cryptsetup handles keyfile differently from cryptosetup itself on plain mode (without LUKS). I have some partitions encrypted using plain mode and the new crypttab syntax does not mount them due to the differences on handling keyfiles. I even fired a bug against systemd explaining the differences and asking for compatibility (https://bugs.freedesktop.org/show_bug.cgi?id=52630) So also for me, unfortunatelly the new syntax (and the usage of systemd-cryptosetup) is also a no-no. Best regards, Marcos