[uefi-secure-boot-guide] f18: Fixed syntax (44173bf)

sparks at fedoraproject.org sparks at fedoraproject.org
Sat Jan 5 02:25:59 UTC 2013


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

On branch  : f18

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

commit 44173bfb3cddeefb5d06a08c71f6533eb52e4d2c
Author: Eric Christensen <sparks at fedoraproject.org>
Date:   Fri Jan 4 21:13:44 2013 -0500

    Fixed syntax


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

 en-US/Implementation_of_Secure_Boot.xml |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/en-US/Implementation_of_Secure_Boot.xml b/en-US/Implementation_of_Secure_Boot.xml
index 024d4cf..013cb7a 100644
--- a/en-US/Implementation_of_Secure_Boot.xml
+++ b/en-US/Implementation_of_Secure_Boot.xml
@@ -14,6 +14,7 @@
 			<member>it will validate the boot command line to only allow certain kernel settings</member>
 			<member>it will check modules at load time for signatures and refuse to load them if they are unsigned or signed with a signature not found in the UEFI key store variables (see note)</member>
 			<member>it will refuse any operations from userland which cause userland-defined DMA.</member>
+		</simplelist>
 	</para>
 	<para>
 	These restrictions are in place to be fully compliant with Secure Boot.  This requires us to prevent any execution of unverified code at the supervisor level.  Most users won't notice these restrictions as most of the userspace packages that required such access have been fixed to work without it.  However, there are a few services or features that will not work in a Secure Boot enabled machine at this time.  They include:
@@ -22,6 +23,7 @@
 			<member>hibernate (suspend to disk)</member>
 			<member>third party modules that are unsigned, or signed with an unknown key</member>
 			<member>systemtap kernel probing (and kprobes)</member>
+		</simplelist>
 	</para>
 	<para>
 	In future iterations of Secure Boot support the above may also be possible, however secure implementations were not feasible in the Fedora 18 timeframe.



More information about the docs-commits mailing list