tldr: Either use your own keys or don't trust secure boot.

Microsoft has yet to explain how or why the lapse occurred.

Highly skilled technical staff are expensive, and it turns out that some people still use Windows when Microsoft doesn't hire the talent necessary to keep Windows working.

Edit: Also, bribes from three letter government agencies are probably pretty nice.

You simply sign a corporate contract and pay a corporate fee, and MICROS~1 will sign any shitty broken and backdoored bootloader that you send to them with zero quality control, and it was like that with Windows drivers for years.

"Complexity is the enemy" is a great quote. Definitely keeping that in my pocket for a future design doc review.

If it says Microslop on it, it's broken.

BY DESIGN

That title is misleading. Maybe people didn't notice that way Secure Boot was broken. But people certainly knows many other ways secure boot is broken.

No wonder no three letter agency has ever complained about it

Or, like me, they never trusted it to begin with.

no one noticed

Did that get Berenstained? I distinctly remember it being broken a decade a ago...

Wasn't there this scandal with Gigabyte motherboards, where Secure Boot showed as enabled, but the motherboards still just booted any unsigned bootcode?!

The gaffe is the result of the failure by Microsoft, which oversees the signing of shims, to revoke the publicly available images once vulnerabilities were found in them.

The only thing I like about Microsoft is that their shit products give me job security.

I get to do an extensive Microsoft Teams training for some middle-aged dudes next week. One of the men doesn't recognize me as someone who can fix his shit. He straight up says, "Have one of your techs, your guys, give me a call" and I always tell him I am a technician and can handle his problem so he doesn't have to wait. I use my kindest, sweetest customer service voice to talk to him and he has never once called me by my name despite it showing on his computer when I connect to it. He calls me honey and dear a lot and not in the endearing old person way.

But dealing with him pays the bills so

OFC. It's probably on purpose.

If you're using Microsoft products, then you care about security theater, legal liability, etc... but not security.

Really funny that, the thing Microsoft used to try and prevent people from using Linux secure systems, was broken this entire time due to laziness revolving around ensuring Linux worked via Secure Boot.

I suspect the headline is incorrect though; likely numerous people knew and were smart enough not to say anything.

I presumed it to be a feature. Yeah. A feature.

We noticed. That's why we started Heads.

Oh I mean I noticed but everyone just called me insane.

Microsoft has yet to explain how or why the lapse occurred.

Because the NSA told them to have that lapse.

Thus they literally cannot legally tell you, that would be a breach of national security.

... are tech writers really this naive?

How is this not obvious?

They're backdoors. It's a lock that's 'secretly' broken, on purpose.

Duh?

Seems to be working well at keeping users from installing Linux.

This is why I haven't trusted the TPM/UEFI & Secure Boot Ecosystem and refused to upgrade my Windows 10 installs to 11 but 10 LTSC, not to mention after a decade of health problems that kept me from using Linux which I had been dabbling in for a few years and using Linux based tools professionally, was one of the reasons that I said " $&#* it, and if I am going to have to spend all this time hacking around my Windows OS to keep it usable and local, I may as well break down and move to Linux!!!".

TSA Agents: "we knew"