News for hackers. Stuff that matters.
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.