Repository :
http://git.fedorahosted.org/git/?p=docs/uefi-secure-boot-guide.git
On branch : master
---------------------------------------------------------------
commit fea9236919b19b66d26e4474e77c4608063f3f19
Author: Peter Jones <pjones(a)redhat.com>
Date: Wed Feb 27 15:12:11 2013 -0500
We really don't need to be recommending attack vectors.
Also there's not a lot of evidence that this is viable anyway, so let's
just not spread FUD.
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 | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/en-US/What_is_Secure_Boot.xml b/en-US/What_is_Secure_Boot.xml
index 886649a..ff445bf 100644
--- a/en-US/What_is_Secure_Boot.xml
+++ b/en-US/What_is_Secure_Boot.xml
@@ -417,8 +417,7 @@ to the end user in any way.
<para>
In the booted operating system, Microsoft Windows 8 supports
AuthentiCode validation and loading of signed third-party kernel
-modules. Hibernation is not disabled, which may provide a venue to
-circumvent UEFI Secure Boot. Windows has infrastructure to extend
+modules. Windows has infrastructure to extend
cryptographic validation to user space programs, again based on
AuthentiCode.
</para>