On Sat, 2026-11-14 at 14:46 +0100, Yves-Alexis Perez wrote: > On Sat, 2026-11-14 at 13:42 +0000, Steve McIntyre wrote: > > > > That should not be an issue here - our 16.1 shim is signed by both the > > old and new Microsoft CAs. > > That's weird because my issue stems from a message when installing shim- > signed:
A bit more information, which is a bit concerning to me:
root@panem:~# mokutil --sb-state
SecureBoot enabled
root@panem:~# dmesg |grep -i secure
[ 0.000000] Kernel is locked down from EFI Secure Boot; see man
kernel_lockdown.7
[ 0.000000] secureboot: Secure boot enabled
[ 0.610660] integrity: Loaded X.509 cert 'Debian Secure Boot CA:
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1'
[ 0.610934] integrity: Loaded X.509 cert 'secure-boot-test-key-lfaraone:
97c1b25cddf9873ca78a58f3d73bf727d2cf78ff'
root@panem:~# efi-readvar
Variable PK has no entries
Variable KEK has no entries
Variable db has no entries
Variable dbx has no entries
Variable MokList has no entries
root@panem:~# ls /sys/firmware/efi/efivars/{PK,KEK,db,dbx}*
ls: cannot access '/sys/firmware/efi/efivars/PK*': No such file or directory
ls: cannot access '/sys/firmware/efi/efivars/KEK*': No such file or directory
ls: cannot access '/sys/firmware/efi/efivars/db*': No such file or directory
ls: cannot access '/sys/firmware/efi/efivars/dbx*': No such file or directory
So how comes SB can be enabled if there's no keys?
Regards,
--
Yves-Alexis
signature.asc
Description: This is a digitally signed message part

