From: Andrew Hamilton <adhamilt@gmail.com>
To: grub-devel@gnu.org
Cc: Andrew Hamilton <adhamilt@gmail.com>,
Daniel Kiper <daniel.kiper@oracle.com>
Subject: [PATCH v4 2/3] docs: Correct chainloader secure boot info
Date: Wed, 30 Oct 2024 19:24:53 -0500 [thread overview]
Message-ID: <20241031002454.3584-3-adhamilt@gmail.com> (raw)
In-Reply-To: <20241031002454.3584-1-adhamilt@gmail.com>
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 <adhamilt@gmail.com>
Reviewed-by: Daniel Kiper <daniel.kiper@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
next prev parent reply other threads:[~2024-10-31 0:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 0:24 [PATCH v4 0/3] docs: Small Fixes for Network, Secure Boot, PXE Andrew Hamilton
2024-10-31 0:24 ` [PATCH v4 1/3] docs: Correct PXE ENV Variable Definitions Andrew Hamilton
2024-10-31 0:24 ` Andrew Hamilton [this message]
2024-10-31 0:24 ` [PATCH v4 3/3] docs: Correct net boot conf name for MAC addr Andrew Hamilton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241031002454.3584-3-adhamilt@gmail.com \
--to=adhamilt@gmail.com \
--cc=daniel.kiper@oracle.com \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.