[Bug 1256730] Re: /usr/share/initramfs-toos/hooks/cryptroot does not honour the CRYPTSETUP variable

[hemmecke]

On 12/02/2013 04:04 AM, Steve Langasek wrote:
>> The problem is that update-initramfs does not put /sbin/cryptsetup
>> into initramfs. My root filesystem is unencrypted but I mount an
>> encrypted partition during boot, so I need cryptsetup in initramfs.

> Why do you think you need cryptsetup in the initramfs for mounting an
> encrypted filesystem that isn't the root filesystem?  This is meant to
> be handled via /etc/init/cryptdisks-udev.conf, with no involvement of
> the initramfs.

Admitted. I might be doing something wrong. To be more clear,
My /etc/fstab looks like this and all is on an USB stick.

UUID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX / ext4
noatime,errors=remount-ro 0
    1
/dev/mapper/vg-lvdata /lvdata   ext4   noatime,errors=remount-ro 0 2
/dev/mapper/vg-lvswap none      swap   sw            0 0
tmpfs                 /tmp      tmpfs  rw            0 0
tmpfs                 /media    tmpfs  rw            0 0
tmpfs                 /mnt      tmpfs  rw            0 0
/lvdata/var           /var      bind   defaults,bind 0 0
/lvdata/root          /root     bind   defaults,bind 0 0
/lvdata/home          /home     bind   defaults,bind 0 0
/lvdata/opt           /opt      bind   defaults,bind 0 0
/lvdata/etc/cups      /etc/cups bind   defaults,bind 0 0
/lvdata/zvol          /zvol     bind   defaults,bind 0 0

Of course, I'd like to setup my system so that nothing is written to the
usb stick at boot time. I have the impression, that works with Raring. I
don't even have /etc/crypttab there.

But apart from my (perhaps wrong) configuration, the problem remains:
/usr/share/initramfs-toos/hooks/cryptroot in Saucy does not honour the
CRYPTSETUP=y setting in /etc/initramfs-tools/initramfs.conf. It should
force putting /sbin/cryptsetup into initramfs (as far as I understand
the meaning of that variable). That's the bug. My setup is actually
irrelevant. I only added it as a hint.

Ralf

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to cryptsetup in Ubuntu.
https://bugs.launchpad.net/bugs/1256730

Title:
  /usr/share/initramfs-toos/hooks/cryptroot does not honour the
  CRYPTSETUP variable

Status in “cryptsetup” package in Ubuntu:
  Incomplete

Bug description:
  The patch https://launchpad.net/ubuntu/+source/cryptsetup/2:1.4.3-4ubuntu4
  checks via

  +if [ -n "$CRYPTSETUP" ] && [ "$CRYPTSETUP" != "n" ]; then
  +    setup="yes"
  +fi

  whether there is CRYPTSETUP=y has been set.

  The description of the patch says that CRYPTSETUP=y in
  /etc/initramfs-tools/initramfs.conf would be enough.
  But it isn't.

  update-initramfs calls mkinitramfs. CRYPTSETUP is still set to y.
  Then /usr/share/initramfs-tools/hooks/cryptroot is called via
  run_scripts/call_scripts. The variable is still set before the
  cryptroot script is entered, but is unset in the script.

  The problem is that update-initramfs does not put /sbin/cryptsetup
  into initramfs. My root filesystem is unencrypted but I mount an
  encrypted partition during boot, so I need cryptsetup in initramfs.

  Ubuntu 13.10

  Ralf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1256730/+subscriptions