Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #903512

Bug#901795: cryptsetup: new version may break 3rd party keyscripts (and thus boot)

Show all headers | View raw

Source: cryptsetup
Version: 2:2.0.3-2
Severity: important


Hi.

Fritst thanks for work you've done in the recent new versions. Sooo many
nice things have been implemented/fixed :-)

Unfortunately, it breaks booting with my personal openpgp keyscripts.

The problem seems that in earlier versions, the initramfs got this file:
main/conf/conf.d/cryptroot with:
target=system,source=/dev/disk/by-uuid/97d2d814-72f6-11e8-a274-742b62897688,rootdev,keyscript=/lib/cryptsetup/scripts/decrypt_openpgp,tries=0,key=device=/dev/disk/by-label/keyFilePart:pathname=/etc/dm-crypt/keys/keyfile_for_system

As you can see, I use the 3rd field of the crypttab, for giving addtional
options to the keyscript:
device=/dev/disk/by-label/keyFilePart		=> the device on which the keyfile is to be found at boot
pathname=/etc/dm-crypt/keys/keyfile_for_sysstem	=> the name of the keyfile on the rootfs of that device

This file is gone, but now there is
main/cryptroot/crypttab with:
system UUID=31a2a126-2947-47ad-a87e-f5b9cb0b6c8a device=/dev/disk/by-label/gss-boot-data_ec713fc2-901a-4f51-8ffe-b9f4df02537b:pathname=/etc/dm-crypt/keys/heisenberg.scientia.net_system loud,luks,keyscript=decrypt_openpgp,tries=0


1) Such a file/format change should go to the NEWS file ;-)
   This is one of the main reasons I reported #826122 back then
   to get that "interface" stable for 3rd party users
2) I assume main/cryptroot/crypttab can have multiple lines, right?
   How can I find out in my keyscript, which one is the right line
   for it right now (i.e. for the device the keyscript currently
   tries to open)?
3) Is there any documentaion of the (stable) format of main/cryptroot/crypttab?
   Cause it doesn't seem to be the same than the normal /etc/crypttab


Thanks,
Chris.

Back to linux.debian.bugs.dist | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Bug#901795: cryptsetup: new version may break 3rd party keyscripts (and thus boot) Christoph Anton Mitterer <calestyo@scientia.net> - 2018-06-18 15:10 +0200
  Bug#901795: cryptsetup: new version may break 3rd party keyscripts (and thus boot) Guilhem Moulin <guilhem@debian.org> - 2018-06-18 20:30 +0200
    Bug#901795: cryptsetup: new version may break 3rd party keyscripts (and thus boot) Christoph Anton Mitterer <calestyo@scientia.net> - 2018-06-19 00:10 +0200
      Bug#901795: cryptsetup: new version may break 3rd party keyscripts (and thus boot) Guilhem Moulin <guilhem@debian.org> - 2018-06-19 00:40 +0200
        Bug#901795: cryptsetup: new version may break 3rd party keyscripts (and thus boot) Christoph Anton Mitterer <calestyo@scientia.net> - 2018-06-25 05:30 +0200
          Bug#901795: cryptsetup: new version may break 3rd party keyscripts (and thus boot) Guilhem Moulin <guilhem@debian.org> - 2018-06-25 15:00 +0200
            Bug#901795: cryptsetup: new version may break 3rd party keyscripts (and thus boot) Christoph Anton Mitterer <calestyo@scientia.net> - 2018-06-26 03:40 +0200
              Bug#901795: cryptsetup: new version may break 3rd party keyscripts (and thus boot) Guilhem Moulin <guilhem@debian.org> - 2018-06-26 04:20 +0200
                Bug#901795: cryptsetup-initramfs: please provide documented shell functions to validate/sanitize cryptroot entries in 3rd party hook files Guilhem Moulin <guilhem@debian.org> - 2018-07-06 23:30 +0200
                Bug#901795: cryptsetup-initramfs: please provide documented shell functions to validate/sanitize cryptroot entries in 3rd party hook files Christoph Anton Mitterer <calestyo@scientia.net> - 2018-07-07 02:00 +0200
                Bug#901795: cryptsetup-initramfs: please provide documented shell functions to validate/sanitize cryptroot entries in 3rd party hook files Guilhem Moulin <guilhem@debian.org> - 2018-07-07 03:20 +0200

csiph-web