Repository :
http://git.fedorahosted.org/git/?p=docs/uefi-secure-boot-guide.git
On branch : master
---------------------------------------------------------------
commit 9ef5bec9e9ac8bea3d679fd758566173ef0609e4
Author: Peter Jones <pjones(a)redhat.com>
Date: Wed Feb 27 15:12:07 2013 -0500
Secure Boot /is/ available on server hardware, just generally disabled.
We shouldn't go saying it doesn't exist on servers or can't be used on
servers - right now there's simply no requirement to enable it on
servers.
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 | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/en-US/What_is_Secure_Boot.xml b/en-US/What_is_Secure_Boot.xml
index 64878b3..338ec4c 100644
--- a/en-US/What_is_Secure_Boot.xml
+++ b/en-US/What_is_Secure_Boot.xml
@@ -103,9 +103,9 @@ a modification has occurred, and simplifies their detection.
<note>
<title>Client Technology</title>
<para>
-UEFI Secure Boot is only available on some client devices, and it is explicitly
-labeled as client (as opposed to server) technology. It is expected that
-server technology will support Secure Boot at a future date.
+UEFI Secure Boot is currently only generally enabled on client devices, and
+is currently not recommended for deployment on server machines. It is
+expected that server technology will enable Secure Boot at a future date.
</para>
</note>
</section>