News for hackers. Stuff that matters.
Re:Exploiting signed bootloaders to circumvent UEFI Secure Boot by bri3d on Sunday February 08, 2026 @01:25PM (#46937020)
> It's really funny to me that Microsoft's attempt to finally stamp out desktop Linux once and for all failed

This conspiracy was never true and never happened. First off, note that the first version of the thing in the article you’re commenting on relied on a Fedora shim loader which Microsoft signed. Second off, note that almost all modern motherboards let you enroll your own UEFI keys and do not rely on exclusively the Microsoft keys.

The only place this is was becoming an issue for Linux was early Secure Boot implementations where the vendor was too lazy to allow key enrollment, and that era has generally passed.

Re:Exploiting signed bootloaders to circumvent UEFI Secure Boot by yjftsjthsd-h on Sunday February 08, 2026 @02:16PM (#46937493)
I don't think it deserves quite that easy a dismissal; MS did lock down early UEFI+ARM devices and prohibit user-controlled keys (see the Windows RT devices as an example). Given their history of playing dirty, it's perfectly reasonable that people assumed this to be another play at undermining Linux, even if things didn't end up going that way.
Re:Exploiting signed bootloaders to circumvent UEFI Secure Boot by bri3d on Sunday February 08, 2026 @03:18PM (#46938116)
By 2019, when the parent article was written, I don't think that was a good read on the situation. By 2026, when the parent comment was written, I really don't think it's a good read on the situation.
Re:Exploiting signed bootloaders to circumvent UEFI Secure Boot by ls612 on Sunday February 08, 2026 @08:02PM (#46940352)
I think that they definitely wanted to iOSify Windows but the colossal failure of Windows 8 and Windows RT led them to take a different approach.
Re:Exploiting signed bootloaders to circumvent UEFI Secure Boot by pbhjpbhj on Sunday February 08, 2026 @02:27PM (#46937602)
It's hard to believe when MS use secure boot to prevent Linux being able to boot. Twice now on my dual boot system a Windows update has prevented Linux being bootable. If it weren't for MS's history one might consider it the accident of a ridiculously inept company.

Even just the lies around required hw updates is enough not to trust them.

SecureBoot looks like a system designed to make it hard to change OS, it has been used by MS for that, MS have a history of user-antagonist actions.

You say the conspiracy was never true, I'm going to need some serious proof.

Re:Exploiting signed bootloaders to circumvent UEFI Secure Boot by NekkoDroid on Sunday February 08, 2026 @02:29PM (#46937628)
> SecureBoot looks like a system designed to make it hard to change OS

To be fair SecureBoot is in a way just that: it is intended to only boot binaries that are signed with a key that has been enrolled into the UEFI. The main issue is like almost always how those keys are managed.

Re:Exploiting signed bootloaders to circumvent UEFI Secure Boot by okanat on Sunday February 08, 2026 @11:34PM (#46941620)
If you buy cheap HW you'll get totally half-assed firmware. It is usually the firmware that causes stupid reordering of the boot entries and weird resets.

Business class computers (Thinkpads, Latitudes or Elitebooks) have somewhat half-assed firmware. So you usually don't encounter shenanigans like that.

Only server computers have almost not half-assed firmware. They are very reliable but take forever to boot.

If you want non-half-assed firmware, found your own computer company or join big tech where they can afford custom motherboards with their own firmware.

Re:Exploiting signed bootloaders to circumvent UEFI Secure Boot by account42 on Monday February 09, 2026 @04:42AM (#46943443)
Of course, Microsoft has always loved Linux and we have always been at war with Eurasia.