[pkg-cryptsetup-devel] Bug#913233: Bug#913233: "/etc/crypttab" ’s manual, an initramfs image can use "/etc/cryptsetup-initramfs/conf-hook" to unlock

[Guilhem Moulin]

Control: tag -1 pending

On Thu, 08 Nov 2018 at 16:03:15 +0100, 21naown at gmail.com wrote:
> An encrypted (root) filesystem containing its key file can be unlocked by
> the initramfs image if the value of the variable “KEYFILE_PATTERN”, in the
> file “/etc/cryptsetup-initramfs/conf-hook”, matches the key file path during
> the generation of the initramfs image.

The use-case is way too narrow IMHO.  crypttab(5) is also relevant
beyond the initramfs stage.  I added a pointer to
/usr/share/doc/cryptsetup-initramfs/README.initramfs.gz in the "See
Also" section.  ‘KEYFILE_PATTERN’ is discussed there (since is it was
introduced in 2:1.7.0-1.

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/20190720/5795c03b/attachment.sig>