Several years ago, when I tried to use the self signed grubx64.efi (grub-efi-amd64-unsigned) it refused to chainload the self signed kernel. So I went with grubx64.efi.signed (grub-efi-amd64-signed), but it depends on shim-signed (shim_lock).
Am Do., 21. Mai 2026 um 12:32 Uhr schrieb Steve McIntyre <[email protected]>: > On Thu, May 21, 2026 at 10:50:23AM +0200, Marc Riedel wrote: > >Package: shim-signed > >Version: 1.50+16.1-2 > >Severity: important > >X-Debbugs-Cc: [email protected] > > > >With the latest changes, the installation of this package fails for now. I > >drive > >several self signed systems with all default certificates removed. So > please > >add the possibility to continue the installation - e.g. a button > "Acknowledged > >and continue, I know what I'm doing!". > > I pondered doing this when I added the extra checks here. > > I have to ask - why are you even installing shim-signed on systems > with SB enabled but where you've removed the default Microsoft > certificates? > > -- > Steve McIntyre, Cambridge, UK. > [email protected] > 'Give me a lever long enough and a Free OS > to set it on, and I can move the world.' > -- Steve Langasek > >
