(replying to #2) Sorry, I didn't see your reply earlier. This could be argued either way as a separate issue or not, but most importantly, the fix for bug 1565950 will also resolve this issue.
For example, if I install vmware and their unsigned kernel modules, I wouldn't be able to use secure boot but may still want an encrypted /boot partition. I had separated out the secure boot aspect from the encrypted /boot aspect. I'm ok if you want to consolidate these issues by resolving this as a duplicate with the acknowledgement that this is a specific issue (specifically the cryptomount portion) of one aspect of bug 1565950. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827928 Title: efi encrypted /boot grub installation does not include crypto support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1827928/+subscriptions -- ubuntu-bugs mailing list email@example.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs