fenced_selinux(8)

1fenced_selinux(8)            SELinux Policy fenced           fenced_selinux(8)
2
3
4

NAME

6       fenced_selinux  -  Security  Enhanced  Linux Policy for the fenced pro‐
7       cesses
8

DESCRIPTION

10       Security-Enhanced Linux  secures  the  fenced  processes  via  flexible
11       mandatory access control.
12
13       The  fenced  processes  execute with the fenced_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 fenced_t
20
21
22

ENTRYPOINTS

24       The  fenced_t  SELinux  type  can be entered via the fenced_exec_t file
25       type.
26
27       The default entrypoint paths for the fenced_t domain are the following:
28
29       /usr/sbin/fenced,      /usr/sbin/fence_node,      /usr/sbin/fence_tool,
30       /usr/sbin/fence_virtd,    /usr/sbin/fence_sanlockd,    /usr/share/clus‐
31       ter/fence_scsi_check,             /usr/share/cluster/fence_mpath_check,
32       /usr/share/cluster/fence_scsi_check.pl,       /usr/lib/systemd/systemd-
33       fence_sanlockd,         /usr/share/cluster/fence_scsi_check_hardreboot,
34       /usr/share/cluster/fence_mpath_check_hardreboot
35

PROCESS TYPES

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

BOOLEANS

57       SELinux  policy is customizable based on least access required.  fenced
58       policy is extremely flexible and has several booleans that allow you to
59       manipulate the policy and run fenced with the tightest access possible.
60
61
62
63       If you want to determine whether fenced can connect to the TCP network,
64       you must turn on the fenced_can_network_connect  boolean.  Disabled  by
65       default.
66
67       setsebool -P fenced_can_network_connect 1
68
69
70
71       If  you  want to determine whether fenced can use ssh, you must turn on
72       the fenced_can_ssh boolean. Disabled by default.
73
74       setsebool -P fenced_can_ssh 1
75
76
77
78       If you want to allow cluster administrative cluster  domains  memcheck-
79       amd64-   to   use  executable  memory,  you  must  turn  on  the  clus‐
80       ter_use_execmem boolean. Disabled by default.
81
82       setsebool -P cluster_use_execmem 1
83
84
85
86       If you want to allow all domains to execute in fips_mode, you must turn
87       on the fips_mode boolean. Enabled by default.
88
89       setsebool -P fips_mode 1
90
91
92

MANAGED FILES

94       The  SELinux  process  type  fenced_t can manage files labeled with the
95       following file types.  The paths listed are the default paths for these
96       file types.  Note the processes UID still need to have DAC permissions.
97
98       cluster_conf_t
99
100            /etc/cluster(/.*)?
101
102       cluster_log
103
104
105       cluster_tmpfs_t
106
107
108       cluster_var_lib_t
109
110            /var/lib/pcsd(/.*)?
111            /var/lib/cluster(/.*)?
112            /var/lib/openais(/.*)?
113            /var/lib/pengine(/.*)?
114            /var/lib/corosync(/.*)?
115            /usr/lib/heartbeat(/.*)?
116            /var/lib/heartbeat(/.*)?
117            /var/lib/pacemaker(/.*)?
118
119       cluster_var_run_t
120
121            /var/run/crm(/.*)?
122            /var/run/cman_.*
123            /var/run/rsctmp(/.*)?
124            /var/run/aisexec.*
125            /var/run/heartbeat(/.*)?
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       fenced_lock_t
134
135            /var/lock/fence_manual.lock
136
137       fenced_tmpfs_t
138
139
140       fenced_var_run_t
141
142            /var/run/fence.*
143            /var/run/cluster/fence_scsi.*
144            /var/run/cluster/mpath.devices
145            /var/run/cluster/fenced_override
146
147       root_t
148
149            /sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
150            /
151            /initrd
152
153       snmpd_var_lib_t
154
155            /var/agentx(/.*)?
156            /var/net-snmp(/.*)
157            /var/lib/snmp(/.*)?
158            /var/net-snmp(/.*)?
159            /var/lib/net-snmp(/.*)?
160            /var/spool/snmptt(/.*)?
161            /usr/share/snmp/mibs/.index
162
163

FILE CONTEXTS

165       SELinux requires files to have an extended attribute to define the file
166       type.
167
168       You can see the context of a file using the -Z option to ls
169
170       Policy governs the access  confined  processes  have  to  these  files.
171       SELinux  fenced  policy  is very flexible allowing users to setup their
172       fenced processes in as secure a method as possible.
173
174       STANDARD FILE CONTEXT
175
176       SELinux defines the file context types for the fenced, if you wanted to
177       store  files  with  these types in a diffent paths, you need to execute
178       the semanage command  to  sepecify  alternate  labeling  and  then  use
179       restorecon to put the labels on disk.
180
181       semanage fcontext -a -t fenced_tmp_t '/srv/myfenced_content(/.*)?'
182       restorecon -R -v /srv/myfenced_content
183
184       Note:  SELinux  often  uses  regular expressions to specify labels that
185       match multiple files.
186
187       The following file types are defined for fenced:
188
189
190
191       fenced_exec_t
192
193       - Set files with the fenced_exec_t type, if you want to  transition  an
194       executable to the fenced_t domain.
195
196
197       Paths:
198            /usr/sbin/fenced,    /usr/sbin/fence_node,   /usr/sbin/fence_tool,
199            /usr/sbin/fence_virtd, /usr/sbin/fence_sanlockd,  /usr/share/clus‐
200            ter/fence_scsi_check,        /usr/share/cluster/fence_mpath_check,
201            /usr/share/cluster/fence_scsi_check.pl,  /usr/lib/systemd/systemd-
202            fence_sanlockd,    /usr/share/cluster/fence_scsi_check_hardreboot,
203            /usr/share/cluster/fence_mpath_check_hardreboot
204
205
206       fenced_lock_t
207
208       - Set files with the fenced_lock_t type, if you want to treat the files
209       as fenced lock data, stored under the /var/lock directory
210
211
212
213       fenced_tmp_t
214
215       -  Set  files  with  the fenced_tmp_t type, if you want to store fenced
216       temporary files in the /tmp directories.
217
218
219
220       fenced_tmpfs_t
221
222       - Set files with the fenced_tmpfs_t type, if you want to  store  fenced
223       files on a tmpfs file system.
224
225
226
227       fenced_var_log_t
228
229       -  Set  files  with the fenced_var_log_t type, if you want to treat the
230       data as fenced var log data, usually stored under the  /var/log  direc‐
231       tory.
232
233
234
235       fenced_var_run_t
236
237       -  Set  files  with the fenced_var_run_t type, if you want to store the
238       fenced files under the /run or /var/run directory.
239
240
241       Paths:
242            /var/run/fence.*,  /var/run/cluster/fence_scsi.*,   /var/run/clus‐
243            ter/mpath.devices, /var/run/cluster/fenced_override
244
245
246       Note:  File context can be temporarily modified with the chcon command.
247       If you want to permanently change the file context you need to use  the
248       semanage fcontext command.  This will modify the SELinux labeling data‐
249       base.  You will need to use restorecon to apply the labels.
250
251

COMMANDS

253       semanage fcontext can also be used to manipulate default  file  context
254       mappings.
255
256       semanage  permissive  can  also  be used to manipulate whether or not a
257       process type is permissive.
258
259       semanage module can also be used to enable/disable/install/remove  pol‐
260       icy modules.
261
262       semanage boolean can also be used to manipulate the booleans
263
264
265       system-config-selinux is a GUI tool available to customize SELinux pol‐
266       icy settings.
267
268

AUTHOR

270       This manual page was auto-generated using sepolicy manpage .
271
272