Secure Boot is completely broken on 200+ models from 5 big device makers (arstechnica.com)
from yogthos@lemmy.ml to technology@lemmy.ml on 26 Jul 2024 11:51
https://lemmy.ml/post/18426106

#technology

threaded - newest

narc0tic_bird@lemm.ee on 26 Jul 2024 14:08 next collapse

I have yet to see a good implementation of Secure Boot, and that’s just from a user interface standpoint.

How can I check which keys are installed in the EFI/BIOS UI? And then delete a specific key? I only ever saw options like “reset to factory settings”.

Factory settings are just Microsoft’s keys most of the time, and often there’s no way to delete/not trust Microsoft’s keys.

The whole system is way too intransparent. May as well turn it off.

Ghoelian@lemmy.dbzer0.com on 26 Jul 2024 14:18 collapse

Yeah, the only thing I’ve ever seen is the MOK management thingy your bios will throw you into if something wants to add a new key, but iirc that can only list the key you’re about to add, not all of them. I also have no idea how you get to that menu without adding a new key.

HubertManne@moist.catsweat.com on 26 Jul 2024 14:58 collapse

I still get issues with efi. I hate these things honestly.

delirious_owl@discuss.online on 26 Jul 2024 15:19 collapse

So basically secure boot as usual? Or is there something new here?

adespoton@lemmy.ca on 27 Jul 2024 03:01 collapse

The new bit is essentially that a bunch of vendors have been using test keys in production hardware, mostly enterprise hardware, and nobody has implemented key clustering or rotation like the original design spec recommended.

Beyond that, the older news is the legitimate production key compromise, stored online behind a four character password. But this one’s not as big an issue as most of the implicated hardware is already EOL and no longer in use.