News for hackers. Stuff that matters.
Re:MSI's (In)Secure Boot by somat on Tuesday January 17, 2023 @06:44AM (#34411395)
The fundamental problem is that someone somewhere decided that setting up signing keys was too hard, and that because of this the manufacturer should be in charge of setting up the keys. so now instead of you owning your hardware and setting up the keys on first boot, Microsoft owns your hardware and the keys are theirs. And in a case of self fulfilling prophecy, because they decided that initializing and owning your own keys was not going to be a normal part of the user experience, it is now hard(almost impossible) to do.

If instead the decision had been made to have the user set up some keys and authorize the OS, the process would have to be streamlined and easy.

In conclusion, signing your operating system is too hard, unless you are in the happy path where your OS is signed by Microsoft it is far easier to just disable the infernal subsystem as it gets in the way.

Re:MSI's (In)Secure Boot by Foxboron on Tuesday January 17, 2023 @06:55AM (#34411461)
> And in a case of self fulfilling prophecy, because they decided that initializing and owning your own keys was not going to be a normal part of the user experience, it is now hard(almost impossible) to do.

This is false.

The issue is that nobody has written user-friendly tooling to manage keys and sign stuff. Not that actually implementing this is hard.

https://github.com/Foxboron/sbctl

Re:MSI's (In)Secure Boot by somat on Tuesday January 17, 2023 @07:32AM (#34411703)
Oh wow, very cool, now I am going to have to try and install my own keys again.