[pkg-cryptsetup-devel] Bug#839994: Bug#839994: Newest version prevent boot of full encrypted disk

[Guilhem Moulin]

Hi Klaus,

On Fri, 07 Oct 2016 at 10:20:08 +0100, Klaus Ethgen wrote:
> However, it was not that easy to create the initramfs as the "most"
> setting for MODULES do not include cryptsetup stuff and "dep" setting
> does not work in a chroot.

Do you have CRYPTSETUP set in your /etc/initramfs-tools/initramfs.conf?
This is an undocumented way of forcing cryptsetup initramfs integration.
As of 2:1.7.2-1, the hook script configuration variable are to be set in
/etc/crytsetup-initramfs/conf-hook, cf. the following changelog entry

  * Use /etc/crytsetup-initramfs/conf-hook for initramfs hook script
    configuration.  For backward compatibility setting CRYPTSETUP and
    KEYFILE_PATTERN in /etc/initramfs-tools/initramfs.conf is still supported
    for now, but causes the hook to print a warning.
    This is done following the initramfs-tools maintainers' request (see
    #807527) that hook and boot script configuration files be stored outside
    the /etc/initramfs-tools directory. (Closes: #783393)

Of course, we didn't intend to break backward compatibility :-/  The
problem here is that sourcing /etc/initramfs-tools/initramfs.conf resets
the CRYPTSETUP variable to the empty string regardless of its previous
value.

-- 
Guilhem.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20161007/415f4bf7/attachment.sig>