← Back to context Comment by nullpoint420 1 month ago Unless it becomes a law, and the hardware makers adapt. 3 comments nullpoint420 Reply palata 1 month ago My Google Pixel allows adding custom keys, which GrapheneOS uses. So I guess that's technically feasible? nullpoint420 1 month ago That adds your custom keys to the fastboot bootloader, not the boot ROM. This means you'd still have to chain your boot through fastboot.You couldn't boot straight from boot ROM -> UEFI for instance. palata 1 month ago Interesting! What's the consequence of that? Like is that a problem?
palata 1 month ago My Google Pixel allows adding custom keys, which GrapheneOS uses. So I guess that's technically feasible? nullpoint420 1 month ago That adds your custom keys to the fastboot bootloader, not the boot ROM. This means you'd still have to chain your boot through fastboot.You couldn't boot straight from boot ROM -> UEFI for instance. palata 1 month ago Interesting! What's the consequence of that? Like is that a problem?
nullpoint420 1 month ago That adds your custom keys to the fastboot bootloader, not the boot ROM. This means you'd still have to chain your boot through fastboot.You couldn't boot straight from boot ROM -> UEFI for instance. palata 1 month ago Interesting! What's the consequence of that? Like is that a problem?
My Google Pixel allows adding custom keys, which GrapheneOS uses. So I guess that's technically feasible?
That adds your custom keys to the fastboot bootloader, not the boot ROM. This means you'd still have to chain your boot through fastboot.
You couldn't boot straight from boot ROM -> UEFI for instance.
Interesting! What's the consequence of that? Like is that a problem?