You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
60 lines
2.3 KiB
60 lines
2.3 KiB
2 years ago
|
From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
|
||
|
|
From: Daniel Axtens <dja@axtens.net>
|
||
|
|
Date: Sat, 15 Aug 2020 02:00:57 +1000
|
||
|
|
Subject: [PATCH] docs/grub: Document signing grub under UEFI
|
||
|
|
|
||
|
|
Before adding information about how grub is signed with an appended
|
||
|
|
signature scheme, it's worth adding some information about how it
|
||
|
|
can currently be signed for UEFI.
|
||
|
|
|
||
|
|
(adjusted from upstream - s/grub/grub2/ in the docs)
|
||
|
|
Signed-off-by: Daniel Axtens <dja@axtens.net>
|
||
|
|
---
|
||
|
|
docs/grub.texi | 19 ++++++++++++++++++-
|
||
|
|
1 file changed, 18 insertions(+), 1 deletion(-)
|
||
|
|
|
||
|
|
diff --git a/docs/grub.texi b/docs/grub.texi
|
||
|
|
index fa11cc0af..acace6c07 100644
|
||
|
|
--- a/docs/grub.texi
|
||
|
|
+++ b/docs/grub.texi
|
||
|
|
@@ -5610,6 +5610,7 @@ environment variables and commands are listed in the same order.
|
||
|
|
@menu
|
||
|
|
* Authentication and authorisation:: Users and access control
|
||
|
|
* Using digital signatures:: Booting digitally signed code
|
||
|
|
+* Signing GRUB itself:: Ensuring the integrity of the GRUB core image
|
||
|
|
@end menu
|
||
|
|
|
||
|
|
@node Authentication and authorisation
|
||
|
|
@@ -5687,7 +5688,7 @@ commands.
|
||
|
|
|
||
|
|
GRUB's @file{core.img} can optionally provide enforcement that all files
|
||
|
|
subsequently read from disk are covered by a valid digital signature.
|
||
|
|
-This document does @strong{not} cover how to ensure that your
|
||
|
|
+This section does @strong{not} cover how to ensure that your
|
||
|
|
platform's firmware (e.g., Coreboot) validates @file{core.img}.
|
||
|
|
|
||
|
|
If environment variable @code{check_signatures}
|
||
|
|
@@ -5772,6 +5773,22 @@ or BIOS) configuration to cause the machine to boot from a different
|
||
|
|
(attacker-controlled) device. GRUB is at best only one link in a
|
||
|
|
secure boot chain.
|
||
|
|
|
||
|
|
+@node Signing GRUB itself
|
||
|
|
+@section Signing GRUB itself
|
||
|
|
+
|
||
|
|
+To ensure a complete secure-boot chain, there must be a way for the code that
|
||
|
|
+loads GRUB to verify the integrity of the core image.
|
||
|
|
+
|
||
|
|
+This is ultimately platform-specific and individual platforms can define their
|
||
|
|
+own mechanisms. However, there are general-purpose mechanisms that can be used
|
||
|
|
+with GRUB.
|
||
|
|
+
|
||
|
|
+@section Signing GRUB for UEFI secure boot
|
||
|
|
+
|
||
|
|
+On UEFI platforms, @file{core.img} is a PE binary. Therefore, it can be signed
|
||
|
|
+with a tool such as @command{pesign} or @command{sbsign}. It will also be
|
||
|
|
+necessary to enrol the public key used into a relevant firmware key database.
|
||
|
|
+
|
||
|
|
@node Platform limitations
|
||
|
|
@chapter Platform limitations
|
||
|
|
|