2 ms·
> My only qualm is that the Google bootloader doesn't show a QR code on boot to verify the kernel image being loaded, instead it simply shows a big yellow warni
by yellowapple 4y ago
> My only qualm is that the Google bootloader doesn't show a QR code on boot to verify the kernel image being loaded, instead it simply shows a big yellow warning saying the OS is unsupported with no way of verifying if it's the GrapheneOS image you loaded or one the maid loaded while you were AFK.
Once upon a time it at least showed part of a hash or somesuch ostensibly uniquely identifying the OS, such that it would change if an Evil Maid flashed a new one.
- Schroedingersat 4y agoThis is the type of thing that happens that happens when you make yourself dependent on someone whose goals are opposed to you by making your OS exclusively for google's phones. I honestly don't know why we can't have a system to visualise the signed image source as the default. Put any public key you want in the firmware, show a 32-64 bit fingerprint of the loaded key as an abstract pattern and only boot an image signed with that key. Manufacturer doesn't get any special treatment. Fairphone at least shows a hash on boot as well as the scary yellow text when relocked. Calyx is available, don't know about graphene.