News for hackers. Stuff that matters.
Re:Exploiting signed bootloaders to circumvent UEFI Secure Boot by invokestatic on Sunday February 08, 2026 @01:26PM (#46937029)
No, this is not true at all. Microsoft requires their system vendors (Dell, HP, etc) to allow users to enroll their own Secure Boot keys through their “Designed for Windows” certification.

Further, many distributions are already compatible with Secure Boot and work out of the box. Whether or not giving Microsoft the UEFI root of trust was a good idea is questionable, but what they DO have is a long, established history of supporting Linux secure boot. They sign a UEFI shim that allows distributions to sign their kernels with their own, distribution-controlled keys in a way that just works on 99% of PCs.

Re:Exploiting signed bootloaders to circumvent UEFI Secure Boot by mhitza on Sunday February 08, 2026 @02:04PM (#46937385)
Is it possible to un-enroll the Microsoft certificates, and just trust the efi shim?
Re:Exploiting signed bootloaders to circumvent UEFI Secure Boot by NekkoDroid on Sunday February 08, 2026 @02:22PM (#46937554)
> Is it possible to un-enroll the Microslop certificates

Technically yes, with a massive fucking asterisk: Some option-ROM are signed with the MS certs and if your Motherboard doesn't support not loading those (whether needed or not) you will not be able to sometimes even POST.

https://github.com/Foxboron/sbctl/wiki/FAQ#option-rom

Re:Exploiting signed bootloaders to circumvent UEFI Secure Boot by bri3d on Sunday February 08, 2026 @02:12PM (#46937458)
With almost all modern motherboard firmware you can enter Setup mode and use KeyTool to configure the trust store however you want, starting from enrolling a user PK (Platform Key) upwards.

It’s generally a lot more secure to avoid the use of any shims (since they leave you vulnerable to what happened in this article) and just build a UEFI Kernel Image and sign that.

Some systems need third party firmware to reach the OS, and this can get a bit more complicated since those modules need to load with the new user keys, but overall what you are asking is generally possible.

Re:Exploiting signed bootloaders to circumvent UEFI Secure Boot by mistrial9 on Sunday February 08, 2026 @02:22PM (#46937562)
> just build a UEFI Kernel Image and sign that.

examples and documentation welcome

Re:Exploiting signed bootloaders to circumvent UEFI Secure Boot by bri3d on Sunday February 08, 2026 @02:26PM (#46937595)
Re:Exploiting signed bootloaders to circumvent UEFI Secure Boot by trelane on Sunday February 08, 2026 @03:26PM (#46938180)