60
Microsoft’s Secure Boot has been broken for a decade and no one noticed until now (arstechnica.com)
submitted 3 months ago by to c/technology@beehaw.org
5 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 33 points 3 months ago (1 child)

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.

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
  • [–] 16 points 3 months ago*

    I mean, UEFI was broken by design from the get-go. It was entirely designed around Windows and shims were an afterthought once the rest of the industry figured out they'd be fucked if they allowed Microsoft complete control. But they didn't fight for an overhaul because Microsoft got all its OEM and BIOS makers on board.

    So shims are the best next thing, and they aren't just about Linux, they're a second PKI layer that allows other entities (than Microsoft) to sign shims. Those entities can be Linux distros but also other OS, software or hardware makers.

    Microsoft forgetting to revoke signatures for old shims is orthogonal to the design, but it's also true that it's not a very good design. Again, because it was originally made to only deal with Windows and does not deal well with other stuff. The article goes into some detail about workarounds on top of workarounds.

  • permalink
  • fedilink
  • source
  • parent