[pkg-cryptsetup-devel] Bug#886007: Bug#886007: cryptsetup: Required /etc/CRYPTTAB OPTION "PLAIN" not documented in "man crypttab" resulting in boot automatic UNLOCK failure

[Guilhem Moulin]

Control: retitle -1 Unify cryptsetup's crypttab(5) and systemd's

Hi,

On Mon, 01 Jan 2018 at 06:01:33 -0800, Harrison wrote:
> The "plain," is undocumented but REQUIRED or the unlock fails during boot.
> […]
> Init: systemd (via /run/systemd/system)

This partition isn't unlocked at initramfs stage (unlike root and resume
devices for instance).  Instead it's taken care of by the normal system,
i.e. systemd in your case.  systemd has its own logic for unlocking
block devices, see systemd-cryptsetup-generator(8).  On Debian systems
crypttab(5) is provided by the 'cryptsetup' package, which doesn't
require the ‘plain’ option; OTOH systemd does, and the option is
documented in its manpage:

    https://www.freedesktop.org/software/systemd/man/crypttab.html

There are inconsistencies between cryptsetup's and systemd's logic, so
we can't have the same manpage for both programs currently.  We should
try to reduce inconsistencies, though.

Cheers,
-- 
Guilhem.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-cryptsetup-devel/attachments/20180519/5df8d8dd/attachment.sig>