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
..
man	Implement syslinux parser.	2013-12-18 05:28:05 +01:00
autoiso.cfg	* docs/autoiso.cfg: New file.	2013-10-27 20:34:24 +01:00
fdl.texi	2008-03-01 Yoshinori K. Okuji <okuji@enbug.org>	2008-03-01 17:27:51 +00:00
font_char_metrics.png	GRUB developper manual based on existing Internals section and	2011-04-03 15:30:28 +02:00
font_char_metrics.txt	GRUB developper manual based on existing Internals section and	2011-04-03 15:30:28 +02:00
grub-dev.texi	gettext: Restore patches to po/Makefile.in.in	2020-03-10 21:17:54 +01:00
grub.cfg	* docs/grub.cfg: Update.	2012-05-04 00:30:15 +02:00
grub.texi	efi: Move the shim_lock verifier to the GRUB core	2021-03-02 15:54:15 +01:00
Makefile.am	Fix make dist.	2012-02-28 12:58:57 +01:00
mdate-sh	2008-03-01 Yoshinori K. Okuji <okuji@enbug.org>	2008-03-01 17:27:51 +00:00
osdetect.cfg	* docs/osdetect.cfg: Add isolinux config to detected OSes.	2013-12-18 05:34:17 +01:00
texinfo.tex	remove all trailing whitespace	2009-06-10 21:04:23 +00:00