Hey Russell On Wed, 2022-12-14 at 08:45 +1100, Russell Coker wrote: > I think this is an upstream bug for misusing an existing config file.
While I agree on that... I'm not sure whether it's good to have two separate config files for more or less the same thing. This might open up all kinds of problems... e.g. administratively (accidentally having the same mapping in both files) but also in terms of support (will tools that parse crypttab suddenly support only one of both?), etc. Would it perhaps be an option for systemd upstream to do something what it already does in /etc/fstab, namely use the x-systemd.* namespace for it's own options? As long as it would do that an otherwise follow the syntax (especially not adding any further columns) it could happily coexist with the "native" cryptsetup format, and e.g. Debian's cryptsetup package could ignore any such entries that have a x-systemd.* option it doesn't understand (or generally all, if that's agreed upon). The only other thing systemd would then need to consider (though Guilhelm might know better if there's more) is that there is a quoting format, in order to allow things like newlines/etc. within a field. Cheers, Chris.
