Correct documentation for secure boot with UEFI to remove statement that chainloader does not work with secure boot, as this was added by a previous GRUB update.
Fixes: https://savannah.gnu.org/bugs/?62004 Signed-off-by: Andrew Hamilton <adham...@gmail.com> Reviewed-by: Daniel Kiper <daniel.ki...@oracle.com> --- docs/grub.texi | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/grub.texi b/docs/grub.texi index 62dace828..5dd4ed84f 100644 --- a/docs/grub.texi +++ b/docs/grub.texi @@ -8678,13 +8678,13 @@ secure boot chain. @node UEFI secure boot and shim @section UEFI secure boot and shim support -The GRUB, except the @command{chainloader} command, works with the UEFI secure -boot and the shim. This functionality is provided by the shim_lock verifier. It -is built into the @file{core.img} and is registered if the UEFI secure boot is -enabled. The @samp{shim_lock} variable is set to @samp{y} when shim_lock verifier -is registered. If it is desired to use UEFI secure boot without shim, one can -disable shim_lock by disabling shim verification with MokSbState UEFI variable -or by building grub image with @samp{--disable-shim-lock} option. +The GRUB works with UEFI secure boot and the shim. This functionality is +provided by the shim_lock verifier. It is built into the @file{core.img} and is +registered if the UEFI secure boot is enabled. The @samp{shim_lock} variable is +set to @samp{y} when shim_lock verifier is registered. If it is desired to use +UEFI secure boot without shim, one can disable shim_lock by disabling shim +verification with MokSbState UEFI variable or by building grub image with +@samp{--disable-shim-lock} option. All GRUB modules not stored in the @file{core.img}, OS kernels, ACPI tables, Device Trees, etc. have to be signed, e.g, using PGP. Additionally, the commands -- 2.39.5 _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
