On Sat, Nov 14, 2026 at 02:32:06PM +0100, Yves-Alexis Perez wrote:
>Running with --verbose I get the following message which might or might not be
>relevant:
>
>13:18:22.891 FuEngine             disabling plugin because: failed to startup
>using uefi_mok: /sys/firmware/efi/mok-variables/HSIStatus does not exist
>
># ls -l /sys/firmware/efi/mok-variables/
>total 0
>-r-------- 1 root root 2630 14 nov.  14:18 MokListRT
>-r-------- 1 root root    1 14 nov.  14:18 MokListTrustedRT
>-r-------- 1 root root 5500 14 nov.  14:18 MokListXRT
>-r-------- 1 root root   46 14 nov.  14:18 SbatLevelRT
>
>Maybe that's because shim-signed is still at 15.8:
>
>ii  shim-helpers-amd64-signed             1+16.1+2~deb13u1                     
>amd64        boot loader to chain-load signed boot loaders (signed by Debian)
>ii  shim-signed:amd64                     1.47+15.8-1                          
>amd64        Secure Boot chain-loading bootloader (Microsoft-signed binary)
>ii  shim-signed-common                    1.51~1+deb13u1+16.1-2~deb13u1        
>all          Secure Boot chain-loading bootloader (common helper scripts)
>ii  shim-unsigned:amd64                   16.1-2~deb13u1                       
>amd64        boot loader to chain-load signed boot loaders under Secure Boot
>
>according to https://fwupd.github.io/libfwupdplugin/uefi-mok-README.html the
>variable is populated at 16+
>
>Unfortunately *if* that plugin is mandatory for the CA update then we have an
>issue because I would need a 16 signed with the older key.

That should not be an issue here - our 16.1 shim is signed by both the
old and new Microsoft CAs.

-- 
Steve McIntyre, Cambridge, UK.                                [email protected]
"Every time you use Tcl, God kills a kitten." -- Malcolm Ray

Reply via email to