[uefi-secure-boot-guide] master: Distinguish between our SB implementation's goals and its mechanism. (98a3580)

[sparks at fedoraproject.org]

Repository : http://git.fedorahosted.org/git/?p=docs/uefi-secure-boot-guide.git

On branch  : master

>---------------------------------------------------------------

commit 98a35806489df4ad4ff27e3344881259d1813224
Author: Peter Jones <pjones at redhat.com>
Date:   Wed Feb 27 15:12:14 2013 -0500

    Distinguish between our SB implementation's goals and its mechanism.
    
    The goal isn't to cryptographically check things - the goal is to stop
    exploits.
    
    Signed-off-by: Peter Jones <pjones at redhat.com>
    Signed-off-by: Eric Christensen <sparks at redhat.com>


>---------------------------------------------------------------

 en-US/What_is_Secure_Boot.xml |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)

diff --git a/en-US/What_is_Secure_Boot.xml b/en-US/What_is_Secure_Boot.xml
index 9b3d950..657134e 100644
--- a/en-US/What_is_Secure_Boot.xml
+++ b/en-US/What_is_Secure_Boot.xml
@@ -429,7 +429,10 @@ AuthentiCode.
 <title>&PRODUCT; Secure Boot</title>
 <para>
 The &PRODUCT; Secure Boot implementation has a single security
-objective: it prevents the execution of unsigned code in kernel mode.
+objective: it prevents installation of a class of malware known as
+<firstterm>boot kits</firstterm> that infect the boot path of the
+machine.  In order to do this, it prevents the execution of unsigned code,
+starting in the boot process and extending to the kernel and its modules.
 </para>
 <para>
 &PRODUCT; can boot on systems with Microsoft Secure Boot enabled,