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

[Steve Langasek]

> 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.

** Changed in: cryptsetup (Ubuntu)
       Status: New => Incomplete

-- 
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