1 |
commit: 51846c0899f8c055fc5f74c33d723eda8380937a |
2 |
Author: Sven Vermeulen <sven.vermeulen <AT> siphos <DOT> be> |
3 |
AuthorDate: Tue May 3 20:22:50 2011 +0000 |
4 |
Commit: Sven Vermeulen <sven.vermeulen <AT> siphos <DOT> be> |
5 |
CommitDate: Tue May 3 20:22:50 2011 +0000 |
6 |
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/hardened-docs.git;a=commit;h=51846c08 |
7 |
|
8 |
Add UBAC FAQ |
9 |
|
10 |
--- |
11 |
xml/selinux-faq.xml | 38 ++++++++++++++++++++++++++++++++++++-- |
12 |
1 files changed, 36 insertions(+), 2 deletions(-) |
13 |
|
14 |
diff --git a/xml/selinux-faq.xml b/xml/selinux-faq.xml |
15 |
index 3922c94..c815ff4 100644 |
16 |
--- a/xml/selinux-faq.xml |
17 |
+++ b/xml/selinux-faq.xml |
18 |
@@ -17,8 +17,8 @@ The FAQ is a collection of solutions found on IRC, mailinglist, forums or |
19 |
elsewhere |
20 |
</abstract> |
21 |
|
22 |
-<version>6</version> |
23 |
-<date>2011-05-01</date> |
24 |
+<version>7</version> |
25 |
+<date>2011-05-03</date> |
26 |
|
27 |
<faqindex> |
28 |
<title>Questions</title> |
29 |
@@ -140,6 +140,40 @@ profiles more flexible and support no-multilib soon. |
30 |
|
31 |
</body> |
32 |
</section> |
33 |
+<section id="ubac"> |
34 |
+<title>What is UBAC exactly?</title> |
35 |
+<body> |
36 |
+ |
37 |
+<p> |
38 |
+UBAC, or <e>User Based Access Control</e>, introduces additional constraints |
39 |
+when using SELinux policy. Participating domains / types that are <e>both</e> |
40 |
+marked as a <c>ubac_constrained_type</c> (which is an attribute) will only |
41 |
+have the allowed privileges in effect if they both run with the same SELinux |
42 |
+user context. |
43 |
+</p> |
44 |
+ |
45 |
+<pre caption="Domains and their SELinux user context"> |
46 |
+<comment># The SELinux allow rule</comment> |
47 |
+allow foo_t bar_t:file { read }; |
48 |
+ |
49 |
+<comment># This will succeed:</comment> |
50 |
+staff_u:staff_r:foo_t reads file with type staff_u:object_r:bar_t |
51 |
+ |
52 |
+<comment># This will be prohibited:</comment> |
53 |
+user_u:user_r:foo_t reads file with type staff_u:object_r:bar_t |
54 |
+</pre> |
55 |
+ |
56 |
+<p> |
57 |
+Of course, this is not always the case. Besides the earlier mentioned |
58 |
+requirement that both types are <c>ubac_constrained_type</c>, if the source |
59 |
+domain is <c>sysadm_t</c>, then the constraint will not be in effect (the |
60 |
+<c>sysadm_t</c> domain is exempt from UBAC constraints). Also, if the source |
61 |
+or destination SELinux user is <c>system_u</c> then the constraint will also |
62 |
+not be in effect. |
63 |
+</p> |
64 |
+ |
65 |
+</body> |
66 |
+</section> |
67 |
</chapter> |
68 |
|
69 |
<chapter> |