you are viewing a single comment's thread
view the rest of the comments
[–] 18 points 7 months ago (7 children)

And this why Secure Boot can't be trusted. It is Micro$lop that signs and issues the keys.

  • source
  • hideshow 7 child comments
  • [–] 24 points 7 months ago (5 children)

    Secure Boot has nothing to do with Microsoft, it's a UEFI feature.

    You can enroll your own Platform Key and have complete control over the entire Secure Boot system.

    https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface/Secure_Boot

    I use a signed Unified Kernel Image to use Secure Boot and my machine has zero Microsoft software on it. (Arch, btw)

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

    wasn't there some dumb shit like every linux distro using fedora keys which were from microsoft?

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 7 months ago* (2 children)

    Microsoft signs Red Hat certs then Red Hat signs everyone's certs, so the only thing Microsoft can do is to revoke Linux as a whole.

    It's the solution that requires minimal user effort since most computers are designed for Windows.

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

    And MS probably won't do it willy-nilly because their stack is peobably using it to some degree and many more of those Fortune-X00 are very likely something RHEL. So fucking that over will crash their stock like it did with CrowdStrike but much much worse.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 14 points 7 months ago*

    You can use custom keys with secure boot. Any PC newer than 2015 should give you that option.

    You don't have to use Microsoft's keys.

    This isn't a secure boot issue. This is a bootloader issue.

  • source
  • parent