| 1 |
commit: 4543642c7b2f7aa8026ac9c864b152743bb62993 |
| 2 |
Author: Sven Vermeulen <sven.vermeulen <AT> siphos <DOT> be> |
| 3 |
AuthorDate: Mon Feb 21 21:55:06 2011 +0000 |
| 4 |
Commit: Sven Vermeulen <sven.vermeulen <AT> siphos <DOT> be> |
| 5 |
CommitDate: Mon Feb 21 21:55:06 2011 +0000 |
| 6 |
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/hardened-docs.git;a=commit;h=4543642c |
| 7 |
|
| 8 |
update preview |
| 9 |
|
| 10 |
--- |
| 11 |
html/selinux-policy.html | 13 +++++++++++-- |
| 12 |
1 files changed, 11 insertions(+), 2 deletions(-) |
| 13 |
|
| 14 |
diff --git a/html/selinux-policy.html b/html/selinux-policy.html |
| 15 |
index de3c47d..b5e715c 100644 |
| 16 |
--- a/html/selinux-policy.html |
| 17 |
+++ b/html/selinux-policy.html |
| 18 |
@@ -25,7 +25,8 @@ |
| 19 |
<b>Content</b>: |
| 20 |
<select name="url" size="1" OnChange="location.href=form.url.options[form.url.selectedIndex].value" style="font-family:sans-serif,Arial,Helvetica"><option value="#doc_chap1">1. Principles</option> |
| 21 |
<option value="#doc_chap2">2. SELinux Domains</option> |
| 22 |
-<option value="#doc_chap3">3. SELinux Roles</option></select> |
| 23 |
+<option value="#doc_chap3">3. SELinux Roles</option> |
| 24 |
+<option value="#doc_chap4">4. SELinux Packages</option></select> |
| 25 |
</form> |
| 26 |
<p class="chaphead"><a name="doc_chap1"></a><span class="chapnum">1. |
| 27 |
</span>Principles</p> |
| 28 |
@@ -185,6 +186,14 @@ SELinux systems, it is hard for a generic policy to create new roles that fit |
| 29 |
the needs of most. We assume that, if there are such roles, then they are |
| 30 |
managed and maintained by the reference policy. |
| 31 |
</p> |
| 32 |
+<p class="chaphead"><a name="doc_chap4"></a><span class="chapnum">4. |
| 33 |
+ </span>SELinux Packages</p> |
| 34 |
+<p class="secthead"><a name="doc_chap4_sect1">Name SELinux Policy Packages After Their Module</a></p> |
| 35 |
+<p> |
| 36 |
+SELinux policy packages should be called after the module they implement (and |
| 37 |
+not the Gentoo package for which the policy would be implemented). The name |
| 38 |
+should use the <span class="path" dir="ltr">sec-policy/selinux-<modname></span> syntax. |
| 39 |
+</p> |
| 40 |
<br><p class="copyright"> |
| 41 |
The contents of this document are licensed under the <a href="http://creativecommons.org/licenses/by-sa/2.5">Creative Commons - |
| 42 |
Attribution / Share Alike</a> license. |
| 43 |
@@ -205,7 +214,7 @@ managed and maintained by the reference policy. |
| 44 |
</td> |
| 45 |
<td width="1%" bgcolor="#dddaec" valign="top"><table border="0" cellspacing="4px" cellpadding="4px"> |
| 46 |
<tr><td class="topsep" align="center"><p class="altmenu"><a title="View a printer-friendly version" class="altlink" href="selinux-policy.xml?style=printable">Print</a></p></td></tr> |
| 47 |
-<tr><td class="topsep" align="center"><p class="alttext">Updated January 21, 2011</p></td></tr> |
| 48 |
+<tr><td class="topsep" align="center"><p class="alttext">Updated February 21, 2011</p></td></tr> |
| 49 |
<tr><td class="topsep" align="left"><p class="alttext"><b>Summary: </b> |
| 50 |
Developing a set of security rules is or should always be done with a common set |
| 51 |
of principles and rules in mind. This document explains the policy used by |
Archives