@defaultusername@lemmy.dbzer0.com
Post #4032628
2026-07-16 04:27 UTC
That’s moreso because it’s using an unofficial key, so the device manufacturer (Google in the case of Pixels) cannot verify the authenticity of the OS you’re running.
If you were able to replace that bootloader with a custom one, then you would be able to disable that message or just use a completely different bootloader like UBoot or EDK2 if it was ported, though.
Replies (1)
-
@01189998819991197253@infosec.pub 2026-07-16 16:52
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.