fenced_selinux(8)
πΈ NAME πΈ
bestie, welcome to fenced_selinux(8) β the Security Enhanced Linux Policy for the fenced processes. This is your little group-chat cheat sheet for all the SELinux fenced lore, and it's giving mandatory access control with main character energy π
.
β¨ DESCRIPTION β¨
Security-Enhanced Linux secures the fenced processes via flexible mandatory access control β no cap, that's the whole vibe.
The fenced processes execute with the fenced_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier.
For example:
ps -eZ | grep fenced_t
π¦ ENTRYPOINTS π¦
The fenced_t SELinux type can be entered via the fenced_exec_t file type.
The default entrypoint paths for the fenced_t domain are literally these:
/usr/bin/fenced
/usr/bin/fence_node
/usr/bin/fence_tool
/usr/bin/fence_virtd
/usr/bin/fence_sanlockd
/usr/share/cluster/fence_scsi_check
/usr/share/cluster/fence_mpath_check
/usr/share/cluster/fence_scsi_check.pl
/usr/lib/systemd/systemd-fence_sanlockd
/usr/share/cluster/fence_scsi_check_hardreboot
/usr/share/cluster/fence_mpath_check_hardreboot
π PROCESS TYPES π
SELinux defines process types (domains) for each process running on the system, periodt.
You can see the context of a process using the -Z option to ps.
Policy governs the access confined processes have to files. SELinux fenced policy is very flexible, allowing users to setup their fenced processes in as secure a method as possible β iconic behavior, honestly.
The following process types are defined for fenced:
fenced_tβ the one and only process type on this list, slay.
Note:semanage permissive -a fenced_tcan be used to make the process typefenced_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated.
π₯ BOOLEANS π₯
SELinux policy is customizable based on least access required. fenced policy is extremely flexible and has several booleans that allow you to manipulate the policy and run fenced with the tightest access possible.
If you want to determine whether fenced can connect to the TCP network, you must turn on the fenced_can_network_connect boolean. Disabled by default.
setsebool -P fenced_can_network_connect 1
If you want to determine whether fenced can use ssh, you must turn on the fenced_can_ssh boolean. Disabled by default.
setsebool -P fenced_can_ssh 1
If you want to allow cluster administrative cluster domains memcheck-amd64- to use executable memory, you must turn on the cluster_use_execmem boolean. Disabled by default.
setsebool -P cluster_use_execmem 1
If you want to dontaudit all daemons scheduling requests (setsched, sys_nice), you must turn on the daemons_dontaudit_scheduling boolean. Enabled by default.
setsebool -P daemons_dontaudit_scheduling 1
If you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean. Enabled by default.
setsebool -P fips_mode 1
If you want to allow system to run with NIS, you must turn on the nis_enabled boolean. Disabled by default.
setsebool -P nis_enabled 1
π MANAGED FILES π
The SELinux process type fenced_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. Note the processes UID still need to have DAC permissions.
cluster_conf_tβ default path time:
/etc/cluster(/.*)?
cluster_logβ it's listed as a managed file type, but this page doesn't spell out default paths for it.cluster_tmpfs_tβ same situation, bestie: listed as a managed file type with no default path list here.cluster_var_lib_tβ default paths:
/var/lib/pcsd(/.*)?
/var/lib/cluster(/.*)?
/var/lib/openais(/.*)?
/var/lib/pengine(/.*)?
/var/lib/corosync(/.*)?
/usr/lib/heartbeat(/.*)?
/var/lib/heartbeat(/.*)?
/var/lib/pacemaker(/.*)?
cluster_var_run_tβ default paths:
/run/crm(/.*)?
/run/cman_.*
/run/rsctmp(/.*)?
/run/aisexec.*
/run/heartbeat(/.*)?
/run/pcsd-ruby.socket
/run/corosync-qnetd(/.*)?
/run/corosync-qdevice(/.*)?
/run/pcsd.socket
/run/corosync.pid
/run/cpglockd.pid
/run/rgmanager.pid
/run/cluster/rgmanager.sk
fenced_lock_tβ default path:
/run/lock/fence_manual.lock
fenced_tmp_tβ listed as a managed file type, with no default path list shown here.fenced_tmpfs_tβ listed as a managed file type too, and again no default paths in this page.fenced_var_run_tβ default paths:
/run/fence.*
/run/cluster/fence_scsi.*
/run/cluster/mpath.devices
/run/cluster/fenced_override
krb5_host_rcache_tβ default paths:
/var/tmp/krb5_0.rcache2
/var/cache/krb5rcache(/.*)?
/var/tmp/nfs_0
/var/tmp/DNS_25
/var/tmp/host_0
/var/tmp/imap_0
/var/tmp/HTTP_23
/var/tmp/HTTP_48
/var/tmp/ldap_55
/var/tmp/ldap_487
/var/tmp/ldapmap1_0
root_tβ default paths:
/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
/var/lib/ntp
snmpd_var_lib_tβ default paths:
/var/agentx(/.*)?
/var/net-snmp(/.*)
/var/lib/snmp(/.*)?
/var/net-snmp(/.*)?
/var/lib/net-snmp(/.*)?
/var/spool/snmptt(/.*)?
/usr/share/snmp/mibs/.index
π FILE CONTEXTS π
SELinux requires files to have an extended attribute to define the file type.
You can see the context of a file using the -Z option to ls.
Policy governs the access confined processes have to these files. SELinux fenced policy is very flexible, allowing users to setup their fenced processes in as secure a method as possible.
β STANDARD FILE CONTEXT β
SELinux defines the file context types for the fenced, and if you wanted to store files with these types in a different paths, you need to execute the semanage command to specify alternate labeling and then use restorecon to put the labels on disk.
semanage fcontext -a -t fenced_exec_t '/srv/fenced/content(/.*)?'
restorecon -R -v /srv/myfenced_content
Note: SELinux often uses regular expressions to specify labels that match multiple files.
The following file types are defined for fenced:
fenced_exec_tβ set files with thefenced_exec_ttype if you want to transition an executable to thefenced_tdomain.
Paths:
/usr/bin/fenced
/usr/bin/fence_node
/usr/bin/fence_tool
/usr/bin/fence_virtd
/usr/bin/fence_sanlockd
/usr/share/cluster/fence_scsi_check
/usr/share/cluster/fence_mpath_check
/usr/share/cluster/fence_scsi_check.pl
/usr/lib/systemd/systemd-fence_sanlockd
/usr/share/cluster/fence_scsi_check_hardreboot
/usr/share/cluster/fence_mpath_check_hardreboot
fenced_lock_tβ set files with thefenced_lock_ttype if you want to treat the files asfencedlock data, stored under the/var/lockdirectory.fenced_tmp_tβ set files with thefenced_tmp_ttype if you want to storefencedtemporary files in the/tmpdirectories.fenced_tmpfs_tβ set files with thefenced_tmpfs_ttype if you want to storefencedfiles on a tmpfs file system.fenced_var_log_tβ set files with thefenced_var_log_ttype if you want to treat the data asfencedvar log data, usually stored under the/var/logdirectory.fenced_var_run_tβ set files with thefenced_var_run_ttype if you want to store thefencedfiles under the/runor/var/rundirectory.
Paths:
/run/fence.*
/run/cluster/fence_scsi.*
/run/cluster/mpath.devices
/run/cluster/fenced_override
Note: File context can be temporarily modified with thechconcommand. If you want to permanently change the file context you need to use thesemanage fcontextcommand. This will modify the SELinux labeling database. You will need to userestoreconto apply the labels.
π COMMANDS π
semanage fcontextcan also be used to manipulate default file context mappings.semanage permissivecan also be used to manipulate whether or not a process type is permissive.semanage modulecan also be used to enable/disable/install/remove policy modules.semanage booleancan also be used to manipulate the booleans.system-config-selinuxis a GUI tool available to customize SELinux policy settings.
π¦ AUTHOR π¦
This manual page was auto-generated using sepolicy manpage .
π SEE ALSO π
selinux(8), fenced(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8)
okay that's the whole page π«Ά β source/version fenced, date 26-10-06, and it's still the fenced_selinux(8) manual, periodt β¨
π¦ where this page comes from
- opensuse-leap 16.0: selinux-policy-doc 20250627+git412.dbf877ab7-160000.1.1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms