Repository :
http://git.fedorahosted.org/git/?p=docs/uefi-secure-boot-guide.git
On branch : master
---------------------------------------------------------------
commit cd07ba242011f62d68e25917e1886d7d378392f1
Author: Peter Jones <pjones(a)redhat.com>
Date: Wed Feb 27 15:12:13 2013 -0500
Don't say some platforms don't support SB correctly.
We don't have any good examples of platforms implementing Secure Boot
incorrectly - the only existing one so far appears to be an accident, and
a fix is in progress. There's no user served by thinking this is a real
problem at this time.
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, 0 insertions(+), 7 deletions(-)
diff --git a/en-US/What_is_Secure_Boot.xml b/en-US/What_is_Secure_Boot.xml
index 338ec4c..9dfc8a3 100644
--- a/en-US/What_is_Secure_Boot.xml
+++ b/en-US/What_is_Secure_Boot.xml
@@ -452,13 +452,6 @@ or enroll the &PRODUCT; certificate.
</para>
</warning>
<para>
-Some systems implement UEFI Secure Boot, but do not follow the
-Microsoft specification and use different certificates. On such
-systems, it is possible to boot &PRODUCT; if the &PRODUCT;
-UEFI Secure Boot certificates have been installed before. This needs
-a different first-stage boot loader.
-</para>
-<para>
&PRODUCT; boots on UEFI systems which do not support or have disabled
Secure Boot, too. This works with all UEFI boot loaders. These boot
loaders also support running in an environment which performs boot