Repository :
http://git.fedorahosted.org/git/?p=docs/uefi-secure-boot-guide.git
On branch : master
---------------------------------------------------------------
commit 4ae52b6c021f845a3fcf32e14292a72658ded76c
Author: Peter Jones <pjones(a)redhat.com>
Date: Wed Feb 27 15:12:03 2013 -0500
Explain Secure Boot as a thing in terms of the system, not the bootloader.
Secure boot isn't a thing the bootloader does - it's a thing the system
does in relation /to/ the bootloader. So our docs should reflect that.
Our bootloader's extension of that into the kernel and so on is a
necessary side effect of that, but it's not the core technology itself.
Signed-off-by: Peter Jones <pjones(a)redhat.com>
Signed-off-by: Eric Christensen <sparks(a)redhat.com>
---------------------------------------------------------------
en-US/What_is_Secure_Boot.xml | 7 +++----
1 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/en-US/What_is_Secure_Boot.xml b/en-US/What_is_Secure_Boot.xml
index 3293933..9b3d950 100644
--- a/en-US/What_is_Secure_Boot.xml
+++ b/en-US/What_is_Secure_Boot.xml
@@ -6,10 +6,9 @@
<chapter id="chap-UEFI_Secure_Boot_Guide-What_is_Secure_Boot">
<title>What is UEFI Secure Boot?</title>
<para>
-<firstterm>Secure Boot</firstterm> is a technology where the system boot
-loader
-checks that the next-stage boot loader is signed with a cryptographic key
-authorized by the configuration of the system boot loader. With adequate
+<firstterm>Secure Boot</firstterm> is a technology where the system firmware
+checks that the system boot loader is signed with a cryptographic key
+authorized by a database contained in the firmware. With adequate
signature verification in the next-stage boot loader(s), kernel, and,
potentially, user space, it is possible to prevent the execution of
unsigned code.