76fb8e4341
The Secure Boot code currently reads the kernel from disk, validates the signature and then reads it from disk again. A sufficiently exciting storage device could modify the kernel between these two events and trigger the execution of an untrusted kernel. Avoid re-reading it in order to ensure this isn't a problem, and in the process speed up boot by not reading the kernel twice. |
||
---|---|---|
.. | ||
coreboot | ||
efi | ||
pc | ||
bsd.c | ||
bsd32.c | ||
bsd64.c | ||
bsd_pagetable.c | ||
bsdXX.c | ||
linux.c | ||
multiboot_mbi.c | ||
verity-hash.h | ||
xen.c | ||
xen_file.c | ||
xen_file32.c | ||
xen_file64.c | ||
xen_fileXX.c | ||
xnu.c |