[pkg-cryptsetup-devel] Bug#776409: cryptsetup fails to unlock volumes with key files from initramfs

[Ben Hutchings]

On Thu, 2015-12-10 at 10:43 +0100, Guilhem Moulin wrote:
> Hi Ben,
> 
> On Fri, 10 Apr 2015 at 02:40:53 +0100, Ben Hutchings wrote:
> > cryptsetup needs to adjust the key file paths when unlocking volumes
> > from the initramfs, because at this point the 'real' root filesystem is
> > mounted at /root.
> 
> Can we really assume in the hook file that the roofs will be mounted
> onto /root?  Indeed the current /usr/share/initramfs-tools/init seems to
> suggest that (it's mounted onto $rootmnt which is constant and set to
> /root).  But this is what initramfs-tools(8) says about rootmnt:
> 
>     Exported variables
>       init sets several variables for the boot scripts environment.
>       […]
>       rootmnt
>         is the path where root gets mounted usually /root.
> 
> Please consider changing the wording (eg, removing “usually”) if we can
> safely make this assumption in hook files.

So don't assume; add $rootmnt to the beginning of the paths.

Ben.

-- 
Ben Hutchings
One of the nice things about standards is that there are so many of them.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 811 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20151211/35b7c924/attachment.sig>