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
..
efifwsetup.c	efi: Return grub_efi_status_t from grub_efi_get_variable()	2020-12-11 13:54:54 +01:00
fixvideo.c	Remove nested functions from PCI iterators.	2013-01-13 01:10:41 +00:00
loadbios.c	verifiers: File type for fine-grained signature-verification controlling	2018-11-09 13:25:31 +01:00
lsefi.c	Fix a segfault in lsefi	2017-08-03 20:03:09 +02:00
lsefimmap.c	lsefimmap: support persistent memory and other UEFI 2.5 features	2015-12-17 21:00:44 +03:00
lsefisystab.c	calloc: Use calloc() at most places	2020-07-29 16:55:47 +02:00
lssal.c	* grub-core/commands/efi/lssal.c: Fix terminating condition.	2013-12-11 15:59:12 +01:00
smbios.c	smbios: Add a module for retrieving SMBIOS information	2019-07-11 21:06:12 +02:00
tpm.c	efi/tpm: Extract duplicate code into independent functions	2020-12-12 01:19:03 +01:00