3 ms·
Security. By default, Chromebooks use a trusted boot path. The boot sequence starts in ROM and the firmware image is verified during boot. Booting unsigned firm
by jdietrich 8y ago
Security. By default, Chromebooks use a trusted boot path. The boot sequence starts in ROM and the firmware image is verified during boot. Booting unsigned firmware is possible but slightly inconvenient by design, to ensure that no user would do this accidentally or as a result of malicious actions.
https://www.chromium.org/chromium-os/chromiumos-design-docs/verified-boot https://www.chromium.org/chromium-os/chromiumos-design-docs/...
- djsumdog 8y agoI don't see why this is specific to Chromebooks. On x86_64/UEFI, I can sign my Grub EFI loader, load my keys into secure book (delete the stock/microsoft ones), re-enable secure boot, password it and now I have a reasonable expectation that I am booting the OS I think I am. It'd be nice if Google opened up their actual bootloader so you could do the same with Chromebooks without needing 3rd party tools.