I don't think this is fixed yet. After switching to the signed grub on
my system with an encrypted boot partition, I get dropped into the grub
command line. From here, the cryptomount command appears to be a no-op.
I'm not sure what the problem is, but I noticed that there is also a
luks module
Package: grub-efi-amd64-signed
Version: 1+2.02+dfsg1+6
Severity: critical
Justification: makes the system completely unbootable
When grub-efi-amd64-signed is installed and /boot is on an encrypted
file system and GRUB_ENABLE_CRYPTODISK=y is present in
/etc/default/grub, the system fails to boot, s
2 matches
Mail list logo
