1bluechi_controller_selinSuExL(i8n)ux Policy bluechi-contbrloulelcehri_controller_selinux(8)
2
3
4

NAME

6       bluechi_controller_selinux  -  Security  Enhanced  Linux Policy for the
7       bluechi-controller processes
8

DESCRIPTION

10       Security-Enhanced Linux secures the  bluechi-controller  processes  via
11       flexible mandatory access control.
12
13       The  bluechi processes execute with the bluechi_t SELinux type. You can
14       check if you have these processes running by executing the  ps  command
15       with the -Z qualifier.
16
17       For example:
18
19       ps -eZ | grep bluechi_t
20
21
22

ENTRYPOINTS

24       The  bluechi_t  SELinux type can be entered via the bluechi_exec_t file
25       type.
26
27       The default entrypoint paths for the bluechi_t domain are  the  follow‐
28       ing:
29
30       /usr/bin/bluechi-controller /usr/libexec/bluechi-controller
31

PROCESS TYPES

33       SELinux defines process types (domains) for each process running on the
34       system
35
36       You can see the context of a process using the -Z option to ps
37
38       Policy governs the access confined processes have  to  files.   SELinux
39       bluechi  policy  is very flexible allowing users to setup their bluechi
40       processes in as secure a method as possible.
41
42       The following process types are defined for bluechi:
43
44       bluechi_t, bluechi_agent_t
45
46       Note: semanage permissive -a bluechi_t can be used to make the  process
47       type  bluechi_t  permissive. SELinux does not deny access to permissive
48       process types, but the AVC (SELinux denials) messages are still  gener‐
49       ated.
50
51

BOOLEANS

53       SELinux policy is customizable based on least access required.  bluechi
54       policy is extremely flexible and has several booleans that allow you to
55       manipulate  the  policy and run bluechi with the tightest access possi‐
56       ble.
57
58
59
60       If you want to dontaudit all  daemons  scheduling  requests  (setsched,
61       sys_nice),  you  must turn on the daemons_dontaudit_scheduling boolean.
62       Enabled by default.
63
64       setsebool -P daemons_dontaudit_scheduling 1
65
66
67
68       If you want to allow all domains to execute in fips_mode, you must turn
69       on the fips_mode boolean. Enabled by default.
70
71       setsebool -P fips_mode 1
72
73
74

PORT TYPES

76       SELinux defines port types to represent TCP and UDP ports.
77
78       You  can  see  the  types associated with a port by using the following
79       command:
80
81       semanage port -l
82
83
84       Policy governs the access  confined  processes  have  to  these  ports.
85       SELinux  bluechi  policy is very flexible allowing users to setup their
86       bluechi processes in as secure a method as possible.
87
88       The following port types are defined for bluechi:
89
90
91       bluechi_port_t
92
93
94
95       Default Defined Ports:
96                 udp 842
97

MANAGED FILES

99       The SELinux process type bluechi_t can manage files  labeled  with  the
100       following file types.  The paths listed are the default paths for these
101       file types.  Note the processes UID still need to have DAC permissions.
102
103       cluster_conf_t
104
105            /etc/cluster(/.*)?
106
107       cluster_var_lib_t
108
109            /var/lib/pcsd(/.*)?
110            /var/lib/cluster(/.*)?
111            /var/lib/openais(/.*)?
112            /var/lib/pengine(/.*)?
113            /var/lib/corosync(/.*)?
114            /usr/lib/heartbeat(/.*)?
115            /var/lib/heartbeat(/.*)?
116            /var/lib/pacemaker(/.*)?
117
118       cluster_var_run_t
119
120            /var/run/crm(/.*)?
121            /var/run/cman_.*
122            /var/run/rsctmp(/.*)?
123            /var/run/aisexec.*
124            /var/run/heartbeat(/.*)?
125            /var/run/pcsd-ruby.socket
126            /var/run/corosync-qnetd(/.*)?
127            /var/run/corosync-qdevice(/.*)?
128            /var/run/corosync.pid
129            /var/run/cpglockd.pid
130            /var/run/rgmanager.pid
131            /var/run/cluster/rgmanager.sk
132
133       initrc_tmp_t
134
135
136       mnt_t
137
138            /mnt(/[^/]*)?
139            /mnt(/[^/]*)?
140            /rhev(/[^/]*)?
141            /rhev/[^/]*/.*
142            /media(/[^/]*)?
143            /media(/[^/]*)?
144            /media/.hal-.*
145            /var/run/media(/[^/]*)?
146            /afs
147            /net
148            /misc
149            /rhev
150
151       root_t
152
153            /sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
154            /
155            /initrd
156
157       tmp_t
158
159            /sandbox(/.*)?
160            /tmp
161            /usr/tmp
162            /var/tmp
163            /var/tmp
164            /tmp-inst
165            /var/tmp-inst
166            /var/tmp/tmp-inst
167            /var/tmp/vi.recover
168
169

FILE CONTEXTS

171       SELinux requires files to have an extended attribute to define the file
172       type.
173
174       You can see the context of a file using the -Z option to ls
175
176       Policy  governs  the  access  confined  processes  have to these files.
177       SELinux bluechi policy is very flexible allowing users to  setup  their
178       bluechi processes in as secure a method as possible.
179
180       STANDARD FILE CONTEXT
181
182       SELinux  defines  the file context types for the bluechi, if you wanted
183       to store files with these types in a different paths, you need to  exe‐
184       cute  the  semanage  command to specify alternate labeling and then use
185       restorecon to put the labels on disk.
186
187       semanage fcontext -a -t bluechi_exec_t '/srv/bluechi/content(/.*)?'
188       restorecon -R -v /srv/mybluechi_content
189
190       Note: SELinux often uses regular expressions  to  specify  labels  that
191       match multiple files.
192
193       The following file types are defined for bluechi:
194
195
196
197       bluechi_agent_exec_t
198
199       -  Set files with the bluechi_agent_exec_t type, if you want to transi‐
200       tion an executable to the bluechi_agent_t domain.
201
202
203
204       bluechi_exec_t
205
206       - Set files with the bluechi_exec_t type, if you want to transition  an
207       executable to the bluechi_t domain.
208
209
210
211       Note:  File context can be temporarily modified with the chcon command.
212       If you want to permanently change the file context you need to use  the
213       semanage fcontext command.  This will modify the SELinux labeling data‐
214       base.  You will need to use restorecon to apply the labels.
215
216

COMMANDS

218       semanage fcontext can also be used to manipulate default  file  context
219       mappings.
220
221       semanage  permissive  can  also  be used to manipulate whether or not a
222       process type is permissive.
223
224       semanage module can also be used to enable/disable/install/remove  pol‐
225       icy modules.
226
227       semanage port can also be used to manipulate the port definitions
228
229       semanage boolean can also be used to manipulate the booleans
230
231
232       system-config-selinux is a GUI tool available to customize SELinux pol‐
233       icy settings.
234
235

AUTHOR

237       This manual page was auto-generated using sepolicy manpage .
238
239

SEE ALSO

241       selinux(8),    bluechi-controller(8),    semanage(8),    restorecon(8),
242       chcon(1),    sepolicy(8),    setsebool(8),    bluechi_agent_selinux(8),
243       bluechi_controller_selinux(8)
244
245
246
247bluechi-controller                 23-04-04      bluechi_controller_selinux(8)
Impressum