Repository :
http://git.fedorahosted.org/git/?p=docs/uefi-secure-boot-guide.git
On branch : fweimer
---------------------------------------------------------------
commit 41b26418e4a5c115684e3bd5ef328f5ce4a52e81
Author: Florian Weimer <fweimer(a)redhat.com>
Date: Wed Feb 13 18:06:34 2013 +0100
Add typical UEFI Secure Boot error message
---------------------------------------------------------------
en-US/What_is_Secure_Boot.xml | 19 ++++++++++++++++++-
1 files changed, 18 insertions(+), 1 deletions(-)
diff --git a/en-US/What_is_Secure_Boot.xml b/en-US/What_is_Secure_Boot.xml
index eed2357..3293933 100644
--- a/en-US/What_is_Secure_Boot.xml
+++ b/en-US/What_is_Secure_Boot.xml
@@ -67,7 +67,10 @@ store).
From a user point of view, a system which has enabled UEFI Secure Boot and which
is confronted with a tampered boot path simply stops working until UEFI Secure
Boot is disabled or a signed next-stage boot loader is available on boot
-media. Similarly, operating system installers
+media.
+(<xref linkend="fig-Secure_Boot-Error_Message"/> shows a typical
+error message.)
+Similarly, operating system installers
without a cryptographically valid signature
do not run and result in an
error message. Users are not offered a way to override the boot loader
@@ -75,6 +78,20 @@ decision to reject the signature, unlike the similar scenario with web
server certificates. No certificate issuer information is provided to the
user.
</para>
+<figure id="fig-Secure_Boot-Error_Message">
+ <title>Typical error message from UEFI Secure Boot</title>
+<literallayout class="monospaced">
+┌────────── Secure Boot Violation ──────────┐
+│ │
+├───────────────────────────────────────────┤
+│ Invalid signature detected. Check Secure │
+│ Boot Policy in Setup │
+│ │
+│ │
+│ [OK] │
+└───────────────────────────────────────────┘
+</literallayout>
+</figure>
<para>
UEFI Secure Boot does not prevent the installation or removal of
second-stage boot loaders or require explicit user confirmation of such