Gentoo Archives: gentoo-commits

From: "Sven Vermeulen (swift)" <swift@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/hardened: selinux-faq.xml
Date: Sat, 29 Sep 2012 16:04:27
Message-Id: 20120929160338.509EB21600@flycatcher.gentoo.org
1 swift 12/09/29 16:03:38
2
3 Modified: selinux-faq.xml
4 Log:
5 Add FAQ on reloading all SELinux policy modules
6
7 Revision Changes Path
8 1.17 xml/htdocs/proj/en/hardened/selinux-faq.xml
9
10 file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/hardened/selinux-faq.xml?rev=1.17&view=markup
11 plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/hardened/selinux-faq.xml?rev=1.17&content-type=text/plain
12 diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/hardened/selinux-faq.xml?r1=1.16&r2=1.17
13
14 Index: selinux-faq.xml
15 ===================================================================
16 RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/hardened/selinux-faq.xml,v
17 retrieving revision 1.16
18 retrieving revision 1.17
19 diff -u -r1.16 -r1.17
20 --- selinux-faq.xml 21 May 2012 19:09:33 -0000 1.16
21 +++ selinux-faq.xml 29 Sep 2012 16:03:38 -0000 1.17
22 @@ -1,6 +1,6 @@
23 <?xml version="1.0" encoding="UTF-8"?>
24 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
25 -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/hardened/selinux-faq.xml,v 1.16 2012/05/21 19:09:33 swift Exp $ -->
26 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/hardened/selinux-faq.xml,v 1.17 2012/09/29 16:03:38 swift Exp $ -->
27
28 <guide>
29 <title>Gentoo Hardened SELinux Frequently Asked Questions</title>
30 @@ -17,8 +17,8 @@
31 elsewhere
32 </abstract>
33
34 -<version>23</version>
35 -<date>2012-05-21</date>
36 +<version>24</version>
37 +<date>2012-09-29</date>
38
39 <faqindex>
40 <title>Questions</title>
41 @@ -948,5 +948,35 @@
42
43 </body>
44 </section>
45 +<section id="reload_all">
46 +<title>How do I reload all SELinux policy modules?</title>
47 +<body>
48 +
49 +<p>
50 +By default, Gentoo incrementally updates the SELinux policy. This is because the
51 +SELinux policy is modularly, starting with a <path>base.pp</path> setting and
52 +then several individual SELinux policy modules. When you install a SELinux
53 +policy package, it first tries to load the individual SELinux policy module. If
54 +that fails however, it will try to (re)load the entire policy (base with all
55 +installed policy modules), akin to the following:
56 +</p>
57 +
58 +<pre caption="(Re)Loading all SELinux policy modules">
59 +<comment># Change "strict" to the policy type you have on your system.</comment>
60 +~# <i>cd /usr/share/selinux/strict</i>
61 +~# <i>semodule -b base.pp -i $(ls *.pp | grep -v unconfined | grep -v base.pp)</i>
62 +
63 +<comment># Or, if you have unconfined domains:</comment>
64 +~# <i>semodule -b base.pp -i $(ls *.pp | grep -v base.pp)</i>
65 +</pre>
66 +
67 +<p>
68 +Failures that occur now usually mean that not all SELinux policy modules have
69 +been upgraded yet, or that there are locally created policies loaded which
70 +cannot coexist with the newly defined SELinux policies.
71 +</p>
72 +
73 +</body>
74 +</section>
75 </chapter>
76 </guide>