Marco A Benatto 5e280caa65 efi: Move the shim_lock verifier to the GRUB core ... Move the shim_lock verifier from its own module into the core image. The Secure Boot lockdown mechanism has the intent to prevent the load of any unsigned code or binary when Secure Boot is enabled. The reason is that GRUB must be able to prevent executing untrusted code if UEFI Secure Boot is enabled, without depending on external modules. Signed-off-by: Marco A Benatto <mbenatto@redhat.com> Signed-off-by: Javier Martinez Canillas <javierm@redhat.com> Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com>		2021-03-02 15:54:15 +01:00
..
acpi.c	tsc: Use alternative delay sources whenever appropriate.	2015-11-27 11:39:55 +01:00
efi.c	efi: Add a function to read EFI variables with attributes	2020-12-11 13:55:31 +01:00
fdt.c	efi: Move fdt helper into own file	2016-11-24 10:09:24 +01:00
init.c	efi: Move the shim_lock verifier to the GRUB core	2021-03-02 15:54:15 +01:00
mm.c	efi: Print error messages to grub_efi_allocate_pages_real()	2020-03-10 21:41:16 +01:00
sb.c	efi: Move the shim_lock verifier to the GRUB core	2021-03-02 15:54:15 +01:00