[Bug 1948598] Re: Can't unlock multiple devices in initramfs

2021-10-28 Thread Niclas Morin
16-1ubuntu0.1 from hirsute-proposed tested in a VM running hirsute installed using the root on zfs guide (for focal). Tested by using the nbde_client ansible role to install clevis and bind two LUKS-encrypted disks to a tang server. It worked as expected. Both disks unlocked during early boot. **

[Bug 1948598] Re: Can't unlock multiple devices in initramfs

2021-10-28 Thread Niclas Morin
Hi Robie! 12-1ubuntu2.3 from focal-proposed tested in a VM by using the nbde_client ansible role to install clevis and bind two LUKS-encrypted disks to a tang server. It worked as expected. Both disks unlocked during early boot. ** Tags removed: verification-needed-focal ** Tags added: verificati

[Bug 1948598] Re: Can't unlock multiple devices in initramfs

2021-10-26 Thread Niclas Morin
@dannf Works like a charm in my test case! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948598 Title: Can't unlock multiple devices in initramfs To manage notifications about this bug go to: http

[Bug 1948598] Re: Can't unlock multiple devices in initramfs

2021-10-25 Thread Niclas Morin
@dannf I would love to! I can do it tomorrow at around this time. Looking forward to it! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948598 Title: Can't unlock multiple devices in initramfs To m

[Bug 1948598] Re: Can't unlock multiple devices in initramfs

2021-10-25 Thread Niclas Morin
** Description changed: - [Impact] + [Impact] clevis can be used to automatically unlock LUKS-encrypted devices during boot by asking a remote server for the key (sort of). It does so by monitoring for the processes that send up the interactive prompts "Please unlock disk xxx:" and then send

[Bug 1948598] Re: Can't unlock multiple devices in initramfs

2021-10-25 Thread Niclas Morin
** Description changed: - It is not possible to unlock multiple devices in the initramfs phase, - for example when having a zfs mirror as the root filesystem. This makes - the package unusable in that case. + [Impact] + clevis can be used to automatically unlock LUKS-encrypted devices during boot

[Bug 1948598] Re: Can't unlock multiple devices in initramfs

2021-10-25 Thread Niclas Morin
@dannf Thank you very much for the help and the information! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948598 Title: Can't unlock multiple devices in initramfs To manage notifications about th

[Bug 1948598] Re: Can't unlock multiple devices in initramfs

2021-10-25 Thread Niclas Morin
@dannf I thought I was filing a bug report for Ubuntu 20.04. Do bugfixes never get backported to previous releases? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948598 Title: Can't unlock multiple

[Bug 1948598] Re: Can't unlock multiple devices in initramfs

2021-10-24 Thread Niclas Morin
** Description changed: It is not possible to unlock multiple devices in the initramfs phase, for example when having a zfs mirror as the root filesystem. This makes the package unusable in that case. - This has been fixed in upstream (latchset/clevis, version 18, commit + This has been f

[Bug 1948598] [NEW] Can't unlock multiple devices in initramfs

2021-10-24 Thread Niclas Morin
Public bug reported: It is not possible to unlock multiple devices in the initramfs phase, for example when having a zfs mirror as the root filesystem. This makes the package unusable in that case. This has been fixed in upstream (latchset/clevis, version 17, commit 0abdfbc7812c8ef588ee22fd35941b

[Bug 1779498] Re: Generates initrd-image with wrong name

2019-02-03 Thread Niclas Morin
What is happening here? No reaction for 6 months? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779498 Title: Generates initrd-image with wrong name To manage notifications about this bug go to: h

[Bug 1814460] [NEW] systemd-cryptsetup fails during initrd stage of boot

2019-02-03 Thread Niclas Morin
Public bug reported: I use Ubuntu 18.04.1 with systemd version: systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid I use dracut + clevis for automatic decr

[Bug 1779498] [NEW] Generates initrd-image with wrong name

2018-06-30 Thread Niclas Morin
Public bug reported: Running 'dracut -f' on Ubuntu 18.04 creates the file /boot/initramfs-4.15.0-23-generic.img. I have to manually move it to overwrite the file /boot/initrd.img-4.15.0-23-generic that is in use. ** Affects: dracut (Ubuntu) Importance: Undecided Status: New ** De

[Bug 1779494] [NEW] Missing dependency

2018-06-30 Thread Niclas Morin
Public bug reported: This package needs the jose package to work correctly. ** Affects: tang (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/177