256
Microsoft’s Secure Boot has been broken for a decade and no one noticed until now (www.welivesecurity.com)
submitted 2 months ago by to c/technology@lemmy.world
63 comments fedilink hide all child comments
 

cross-posted from: https://piefed.world/c/tech/p/1263218/microsofts-secure-boot-has-been-broken-for-a-decade-and-no-one-noticed-until-now

you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 2 months ago (8 children)

Functionally, though, wouldn't it be the same as replacing the computer's SecureBoot bootloader, since it's Microsoft (in the case of SecureBoot) that doesn't like the unofficial key that Linux installs? Shouldn't the user be allowed to add or remove any key they desire from the allow list of official keys (maybe have some sort of decentralized verification system, if they user decides they want to verify it)?

I'm more thinking out loud here, trying to understand.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] 3 points 2 months ago (7 children)

    The difference is that with ARM TrustZone, there is an efuse burned with the key that the manufacturer set in the SoC itself that checks the signature of the primary bootloader, which cannot be modified.

    Standard computers do not have such a hardware-level key, so if you wanted to replace the bootloader with something like coreboot if it has been ported to your board, then you can. On smartphones, you do not have that option.

    Same thing goes for even more locked down systems like game consoles.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 1 point 2 months ago (6 children)

    Ah, that makes a lot more sense!

    Is there no way to clear that memory? Or is it more just that it's uncommonly difficult that the people with the skillset just do other, more value added things?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 3 points 2 months ago* (5 children)

    It's not memory, but rather physical fuses that have been blown on the die itself, similar to the Xbox 360's downgrade protection fuses and CPU key. Much like the Xbox 360, the only way to bypass it would be to do something like a reset glitch hack to glitch the state of the CPU right as it tries to read the state of the fuses and bypass that check, and that would require a specific modchip for every individual device. Another option would be to replace the SoC with one that does not have that protection enabled to begin with.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 2 points 2 months ago (4 children)

    I was unaware of this. Super interesting, and disturbing honesty.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 2 months ago (3 children)

    Yeah. Best to look out for devices that don't have this restriction. Not 100% sure if the Fairphone and Shiftphone have this, but I'm sure if you ask them, they'll tell you.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 2 months ago* (2 children)

    I think the nothing phone does not have it, at least, i doubt because their bootloader is not locked IIRC

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •