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: Sun, 30 Oct 2011 12:13:38
Message-Id: 20111030121327.A89212004B@flycatcher.gentoo.org
1 swift 11/10/30 12:13:27
2
3 Modified: selinux-faq.xml
4 Log:
5 Style updates, no content change
6
7 Revision Changes Path
8 1.10 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.10&view=markup
11 plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/hardened/selinux-faq.xml?rev=1.10&content-type=text/plain
12 diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/hardened/selinux-faq.xml?r1=1.9&r2=1.10
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.9
18 retrieving revision 1.10
19 diff -u -r1.9 -r1.10
20 --- selinux-faq.xml 28 Oct 2011 17:59:41 -0000 1.9
21 +++ selinux-faq.xml 30 Oct 2011 12:13:27 -0000 1.10
22 @@ -1,8 +1,8 @@
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.9 2011/10/28 17:59:41 nimiux Exp $ -->
26 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/hardened/selinux-faq.xml,v 1.10 2011/10/30 12:13:27 swift Exp $ -->
27
28 -<guide>
29 +<guide link="/proj/en/hardened/selinux-faq.xml" lang="en">
30 <title>Gentoo Hardened SELinux Frequently Asked Questions</title>
31 <author title="Author">
32 <mail link="pebenito@g.o">Chris PeBenito</mail>
33 @@ -252,7 +252,9 @@
34 </body>
35 </section>
36 <section id="matchcontext">
37 -<title>How do I know which file context rule is used for a particular file?</title>
38 +<title>
39 + How do I know which file context rule is used for a particular file?
40 +</title>
41 <body>
42
43 <p>
44 @@ -396,8 +398,8 @@
45 </p>
46
47 <p>
48 -When using interface names, make sure that the types (<c>ssh_t</c> and
49 -<c>user_t</c>) are mentioned in the <c>require { ... }</c> paragraph.
50 +When using interface names, make sure that the type (<c>ssh_t</c> and
51 +<c>user_t</c>) is mentioned in the <c>require { ... }</c> paragraph.
52 </p>
53
54 <p>
55 @@ -588,8 +590,10 @@
56 </body>
57 </section>
58 <section id="portage_libsandbox">
59 -<title>During package installation, ld.so complains 'object 'libsandbox.so'
60 -from LD_PRELOAD cannot be preloaded: ignored'</title>
61 +<title>
62 + During package installation, ld.so complains 'object 'libsandbox.so' from
63 + LD_PRELOAD cannot be preloaded: ignored'
64 +</title>
65 <body>
66
67 <p>
68 @@ -659,8 +663,10 @@
69 </body>
70 </section>
71 <section id="cronfails">
72 -<title>Cron fails to load in root's crontab with message '(root) ENTRYPOINT
73 -FAILED (crontabs/root)'</title>
74 +<title>
75 + Cron fails to load in root's crontab with message '(root) ENTRYPOINT
76 + FAILED (crontabs/root)'
77 +</title>
78 <body>
79
80 <p>
81 @@ -777,7 +783,7 @@
82 </p>
83
84 <p>
85 -The solution is to rebuild policycoreutils while disabling Portage's selinux
86 +The solution is to rebuild policycoreutils while disabling Portage' selinux
87 support, then label the installed files manually using <c>chcon</c>, based on
88 the feedback received from <c>matchpathcon</c>.
89 </p>