Comment by morpheuskafka
9 days ago
> custom ways of doing things, instead of furthering efforts like UEFI on ARM.
I thought uBoot was more or less the standard way of booting embedded Linux? Is it really worth bringing the entire UEFI environment, which is basically a mini OS, to such devices? Embedded devices are often designed to handle power loss or even be unplugged by users, so the boot up process is generally as lean as possible.
U-Boot nowadays speaks UEFI :) (and so does LK)
New Android devices all use a UEFI bootloader: https://source.android.com/docs/core/architecture/bootloader...
SecureBoot might be more useful than UEFI on SBC like Pi.
The grub EFI shim is signed, but does or doesn't verify kernel image and initrd and module (and IDK optionally drive and CPU and RAM hw) signatures?
mokutil does module signature key enrollment. Kernel modules must be signed with a key enrolled in the BIOS otherwise they won't be loaded.
To implement SecureBoot without UEFI would be to develop an alternate bootloader verification system.
But what does grub or uboot or p-boot do after the signed grub shim is verified?
mokutil and these commands don't work without UEFI:
Note that UEFI doesn't mean supporting most of those.
UEFI without runtime UEFI variable writes is a thing, and that configuration is incompatible with mokutil.
3 replies →