f4d00290ed
If grub is signed with a key that's in the trusted EFI keyring, an attacker can point a boot entry at grub rather than at shim and grub will fail to locate the shim verification protocol. This would then allow booting an arbitrary kernel image. Fail validation if Secure Boot is enabled and we can't find the shim protocol in order to prevent this. |
||
|---|---|---|
| .. | ||
| coreboot | ||
| efi | ||
| pc | ||
| bsd.c | ||
| bsd32.c | ||
| bsd64.c | ||
| bsdXX.c | ||
| bsd_pagetable.c | ||
| linux.c | ||
| multiboot_mbi.c | ||
| xen.c | ||
| xen_file.c | ||
| xen_file32.c | ||
| xen_file64.c | ||
| xen_fileXX.c | ||
| xnu.c | ||