Control: tag -1 + upstream Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=52630 Control: retitle -1 systemd-cryptsetup handles keyfile differently from cryptsetup on plain mode
Hi again, intrigeri wrote (16 Nov 2014 18:32:58 GMT) : > Could you please try to pinpoint which exact option, among the many > ones you're using, is badly handled? > E.g. start with a plain dm-crypt device, then use an external key > file, then add cipher/hash/offset/retry options one at a time. Actually, this seems to be a known upstream bug [1]. The archlinux wiki [2] says: Warning: An unresolved systemd bug exists in the crypttab processing logic for dm-crypt --type plain devices with a keyfile. Do not use crypttab for those and do not use systemd-cryptsetup to work around it! If you have to, a workaround is to use a small script calling cryptsetup using the plain mode options with the keyfile to open and mount such devices during boot instead. [1] https://bugs.freedesktop.org/show_bug.cgi?id=52630 [2] https://wiki.archlinux.org/index.php/Dm-crypt/System_configuration#crypttab Cheers, -- intrigeri _______________________________________________ Pkg-systemd-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
