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:

│ No valid UEFI Secure Boot signatures found                                 
│ 
   │                                                                         
│ 
   │ UEFI Secure Boot is enabled on your system, but the signed shim binary in
this package is not signed with a key that your system trusts. This is a   │ 
   │ FATAL ERROR - your system will not currently boot with this signed shim
installed.                                                                   │
   │                                                                         
│ 
   │ To fix this error, you probably need to update the trusted certificates
list (DB) on your system. See                                                │
   │                                                                         
│ 
   │ https://wiki.debian.org/SecureBoot/CAChanges                            
│ 
   │                                                                         
│ 
   │ for more information about how to do this.     

For shim-signed_1.51~1+deb13u1+16.1-2~deb13u1_amd64.deb                      
-- 
Yves-Alexis

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to