3 ms·
> It seems to add a lot of complexity, and offers no real world usecases. The use case for kernel lockdown has to do with being a good player in the Secure Boo
by zozbot234 6y ago
> It seems to add a lot of complexity, and offers no real world usecases.
The use case for kernel lockdown has to do with being a good player in the Secure Boot ecosystem so that kernel images can be signed by default. If a malicious user can boot the kernel in secure boot mode and then get it to execute code in ring0 that chainloads a different OS while staying in secure boot mode and with the user being none the wiser, this subverts the ecosystem since the other OS will lose its pre-existing guarantees about system state. Note that the EFI "shim" executable does allow for chainloading an OS in secure mode but only after prompting the user to that effect.
- lima 6y agoIsn't that kind of a lost fight? So many signed bootloaders and no way to revoke in-the-wild.
- londons_explore 6y agoJust make the linux kernel modify the TPM state in some way on startup? Then any chainloaded OS would be able to see it isn't running on bare metal.