1fenced_selinux(8) SELinux Policy fenced fenced_selinux(8)
2
6 fenced_selinux - Security Enhanced Linux Policy for the fenced pro‐
7 cesses
8
10 Security-Enhanced Linux secures the fenced processes via flexible
11 mandatory access control.
12 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 For example:
18 ps -eZ | grep fenced_t
20
24 The fenced_t SELinux type can be entered via the fenced_exec_t file
25 type.
26 The default entrypoint paths for the fenced_t domain are the following:
28 /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
37 SELinux defines process types (domains) for each process running on the
38 system
39 You can see the context of a process using the -Z option to ps
41 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 The following process types are defined for fenced:
47 fenced_t
49 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
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 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 setsebool -P fenced_can_network_connect 1
68 If you want to determine whether fenced can use ssh, you must turn on
72 the fenced_can_ssh boolean. Disabled by default.
73 setsebool -P fenced_can_ssh 1
75 If you want to allow cluster administrative cluster domains memcheck-
79 amd64- to use executable memory, you must turn on the cluster_use_ex‐
80 ecmem boolean. Disabled by default.
81 setsebool -P cluster_use_execmem 1
83 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 setsebool -P fips_mode 1
90
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 cluster_conf_t
99 /etc/cluster(/.*)?
101 cluster_log
103 cluster_tmpfs_t
106 cluster_var_lib_t
109 /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 cluster_var_run_t
120 /var/run/crm(/.*)?
122 /var/run/cman_.*
123 /var/run/rsctmp(/.*)?
124 /var/run/aisexec.*
125 /var/run/heartbeat(/.*)?
126 /var/run/pcsd-ruby.socket
127 /var/run/corosync-qnetd(/.*)?
128 /var/run/corosync-qdevice(/.*)?
129 /var/run/corosync.pid
130 /var/run/cpglockd.pid
131 /var/run/rgmanager.pid
132 /var/run/cluster/rgmanager.sk
133 fenced_lock_t
135 /var/lock/fence_manual.lock
137 fenced_tmp_t
139 fenced_tmpfs_t
142 fenced_var_run_t
145 /var/run/fence.*
147 /var/run/cluster/fence_scsi.*
148 /var/run/cluster/mpath.devices
149 /var/run/cluster/fenced_override
150 krb5_host_rcache_t
152 /var/tmp/krb5_0.rcache2
154 /var/cache/krb5rcache(/.*)?
155 /var/tmp/nfs_0
156 /var/tmp/DNS_25
157 /var/tmp/host_0
158 /var/tmp/imap_0
159 /var/tmp/HTTP_23
160 /var/tmp/HTTP_48
161 /var/tmp/ldap_55
162 /var/tmp/ldap_487
163 /var/tmp/ldapmap1_0
164 root_t
166 /sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
168 /
169 /initrd
170 snmpd_var_lib_t
172 /var/agentx(/.*)?
174 /var/net-snmp(/.*)
175 /var/lib/snmp(/.*)?
176 /var/net-snmp(/.*)?
177 /var/lib/net-snmp(/.*)?
178 /var/spool/snmptt(/.*)?
179 /usr/share/snmp/mibs/.index
180
183 SELinux requires files to have an extended attribute to define the file
184 type.
185 You can see the context of a file using the -Z option to ls
187 Policy governs the access confined processes have to these files.
189 SELinux fenced policy is very flexible allowing users to setup their
190 fenced processes in as secure a method as possible.
191 STANDARD FILE CONTEXT
193 SELinux defines the file context types for the fenced, if you wanted to
195 store files with these types in a diffent paths, you need to execute
196 the semanage command to sepecify alternate labeling and then use re‐
197 storecon to put the labels on disk.
198 semanage fcontext -a -t fenced_tmp_t '/srv/myfenced_content(/.*)?'
200 restorecon -R -v /srv/myfenced_content
201 Note: SELinux often uses regular expressions to specify labels that
203 match multiple files.
204 The following file types are defined for fenced:
206 fenced_exec_t
210 - Set files with the fenced_exec_t type, if you want to transition an
212 executable to the fenced_t domain.
213 Paths:
216 /usr/sbin/fenced, /usr/sbin/fence_node, /usr/sbin/fence_tool,
217 /usr/sbin/fence_virtd, /usr/sbin/fence_sanlockd, /usr/share/clus‐
218 ter/fence_scsi_check, /usr/share/cluster/fence_mpath_check,
219 /usr/share/cluster/fence_scsi_check.pl, /usr/lib/systemd/systemd-
220 fence_sanlockd, /usr/share/cluster/fence_scsi_check_hardreboot,
221 /usr/share/cluster/fence_mpath_check_hardreboot
222 fenced_lock_t
225 - Set files with the fenced_lock_t type, if you want to treat the files
227 as fenced lock data, stored under the /var/lock directory
228 fenced_tmp_t
232 - Set files with the fenced_tmp_t type, if you want to store fenced
234 temporary files in the /tmp directories.
235 fenced_tmpfs_t
239 - Set files with the fenced_tmpfs_t type, if you want to store fenced
241 files on a tmpfs file system.
242 fenced_var_log_t
246 - Set files with the fenced_var_log_t type, if you want to treat the
248 data as fenced var log data, usually stored under the /var/log direc‐
249 tory.
250 fenced_var_run_t
254 - Set files with the fenced_var_run_t type, if you want to store the
256 fenced files under the /run or /var/run directory.
257 Paths:
260 /var/run/fence.*, /var/run/cluster/fence_scsi.*, /var/run/clus‐
261 ter/mpath.devices, /var/run/cluster/fenced_override
262 Note: File context can be temporarily modified with the chcon command.
265 If you want to permanently change the file context you need to use the
266 semanage fcontext command. This will modify the SELinux labeling data‐
267 base. You will need to use restorecon to apply the labels.
268
271 semanage fcontext can also be used to manipulate default file context
272 mappings.
273 semanage permissive can also be used to manipulate whether or not a
275 process type is permissive.
276 semanage module can also be used to enable/disable/install/remove pol‐
278 icy modules.
279 semanage boolean can also be used to manipulate the booleans
281 system-config-selinux is a GUI tool available to customize SELinux pol‐
284 icy settings.
285
288 This manual page was auto-generated using sepolicy manpage .
289
292 selinux(8), fenced(8), semanage(8), restorecon(8), chcon(1), sepol‐
293 icy(8), setsebool(8)
294fenced 21-06-09 fenced_selinux(8)