mirror of
https://git.proxmox.com/git/efi-boot-shim
synced 2025-06-05 20:35:06 +00:00
Don't hook system services if shim has no built-in keys
Shim should only need to enforce its security policy when its launching binaries signed with its built-in key. Binaries signed by keys in db or Mokdb should be able to rely on their own security policy. Signed-off-by: Matthew Garrett <matthew.garrett@nebula.com>
This commit is contained in:
parent
d95b24bd02
commit
8b48ec5c70
14
shim.c
14
shim.c
@ -1757,11 +1757,15 @@ EFI_STATUS efi_main (EFI_HANDLE image_handle, EFI_SYSTEM_TABLE *passed_systab)
|
||||
Print(L"Booting in insecure mode\n");
|
||||
uefi_call_wrapper(BS->Stall, 1, 2000000);
|
||||
} else if (secure_mode()) {
|
||||
/*
|
||||
* Install our hooks for ExitBootServices() and StartImage()
|
||||
*/
|
||||
hook_system_services(systab);
|
||||
loader_is_participating = 0;
|
||||
if (vendor_cert_size || vendor_dbx_size) {
|
||||
/*
|
||||
* If shim includes its own certificates then ensure
|
||||
* that anything it boots has performed some
|
||||
* validation of the next image.
|
||||
*/
|
||||
hook_system_services(systab);
|
||||
loader_is_participating = 0;
|
||||
}
|
||||
}
|
||||
|
||||
/*
|
||||
|
Loading…
Reference in New Issue
Block a user