Current File : //usr/share/selinux/devel/html/fenced.html
<!-- Creator     : groff version 1.22.4 -->
<!-- CreationDate: Thu Apr 10 20:00:00 2025 -->
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta name="generator" content="groff -Thtml, see www.gnu.org">
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<meta name="Content-Style" content="text/css">
<style type="text/css">
       p       { margin-top: 0; margin-bottom: 0; vertical-align: top }
       pre     { margin-top: 0; margin-bottom: 0; vertical-align: top }
       table   { margin-top: 0; margin-bottom: 0; vertical-align: top }
       h1      { text-align: center }
</style>
<title>fenced_selinux</title>

</head>
<body>

<h1 align="center">fenced_selinux</h1>

<a href="#NAME">NAME</a><br>
<a href="#DESCRIPTION">DESCRIPTION</a><br>
<a href="#ENTRYPOINTS">ENTRYPOINTS</a><br>
<a href="#PROCESS TYPES">PROCESS TYPES</a><br>
<a href="#BOOLEANS">BOOLEANS</a><br>
<a href="#MANAGED FILES">MANAGED FILES</a><br>
<a href="#FILE CONTEXTS">FILE CONTEXTS</a><br>
<a href="#COMMANDS">COMMANDS</a><br>
<a href="#AUTHOR">AUTHOR</a><br>
<a href="#SEE ALSO">SEE ALSO</a><br>

<hr>


<h2>NAME
<a name="NAME"></a>
</h2>


<p style="margin-left:11%; margin-top: 1em">fenced_selinux
&minus; Security Enhanced Linux Policy for the fenced
processes</p>

<h2>DESCRIPTION
<a name="DESCRIPTION"></a>
</h2>



<p style="margin-left:11%; margin-top: 1em">Security-Enhanced
Linux secures the fenced processes via flexible mandatory
access control.</p>

<p style="margin-left:11%; margin-top: 1em">The fenced
processes execute with the fenced_t SELinux type. You can
check if you have these processes running by executing the
<b>ps</b> command with the <b>&minus;Z</b> qualifier.</p>

<p style="margin-left:11%; margin-top: 1em">For
example:</p>

<p style="margin-left:11%; margin-top: 1em"><b>ps -eZ |
grep fenced_t</b></p>

<h2>ENTRYPOINTS
<a name="ENTRYPOINTS"></a>
</h2>


<p style="margin-left:11%; margin-top: 1em">The fenced_t
SELinux type can be entered via the <b>fenced_exec_t</b>
file type.</p>

<p style="margin-left:11%; margin-top: 1em">The default
entrypoint paths for the fenced_t domain are the
following:</p>


<p style="margin-left:11%; margin-top: 1em">/usr/sbin/fenced,
/usr/sbin/fence_node, /usr/sbin/fence_tool,
/usr/sbin/fence_virtd, /usr/sbin/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</p>

<h2>PROCESS TYPES
<a name="PROCESS TYPES"></a>
</h2>


<p style="margin-left:11%; margin-top: 1em">SELinux defines
process types (domains) for each process running on the
system</p>

<p style="margin-left:11%; margin-top: 1em">You can see the
context of a process using the <b>&minus;Z</b> option to
<b>ps</b></p>

<p style="margin-left:11%; margin-top: 1em">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.</p>

<p style="margin-left:11%; margin-top: 1em">The following
process types are defined for fenced:</p>


<p style="margin-left:11%; margin-top: 1em"><b>fenced_t</b></p>

<p style="margin-left:11%; margin-top: 1em">Note:
<b>semanage permissive -a fenced_t</b> can be used to make
the process type fenced_t permissive. SELinux does not deny
access to permissive process types, but the AVC (SELinux
denials) messages are still generated.</p>

<h2>BOOLEANS
<a name="BOOLEANS"></a>
</h2>


<p style="margin-left:11%; margin-top: 1em">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.</p>

<p style="margin-left:11%; margin-top: 1em">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.</p>

<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
fenced_can_network_connect 1</b></p>

<p style="margin-left:11%; margin-top: 1em">If you want to
determine whether fenced can use ssh, you must turn on the
fenced_can_ssh boolean. Disabled by default.</p>

<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
fenced_can_ssh 1</b></p>

<p style="margin-left:11%; margin-top: 1em">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.</p>

<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
cluster_use_execmem 1</b></p>

<p style="margin-left:11%; margin-top: 1em">If you want to
dontaudit all daemons scheduling requests (setsched,
sys_nice), you must turn on the daemons_dontaudit_scheduling
boolean. Enabled by default.</p>

<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
daemons_dontaudit_scheduling 1</b></p>

<p style="margin-left:11%; margin-top: 1em">If you want to
allow all domains to execute in fips_mode, you must turn on
the fips_mode boolean. Enabled by default.</p>

<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
fips_mode 1</b></p>

<p style="margin-left:11%; margin-top: 1em">If you want to
allow system to run with NIS, you must turn on the
nis_enabled boolean. Disabled by default.</p>

<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
nis_enabled 1</b></p>

<h2>MANAGED FILES
<a name="MANAGED FILES"></a>
</h2>


<p style="margin-left:11%; margin-top: 1em">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.</p>


<p style="margin-left:11%; margin-top: 1em"><b>cluster_conf_t</b></p>


<p style="margin-left:11%; margin-top: 1em">/etc/cluster(/.*)?</p>


<p style="margin-left:11%; margin-top: 1em"><b>cluster_log</b></p>


<p style="margin-left:11%; margin-top: 1em"><b>cluster_tmpfs_t</b></p>


<p style="margin-left:11%; margin-top: 1em"><b>cluster_var_lib_t</b></p>


<p style="margin-left:11%; margin-top: 1em">/var/lib/pcsd(/.*)?
<br>
/var/lib/cluster(/.*)? <br>
/var/lib/openais(/.*)? <br>
/var/lib/pengine(/.*)? <br>
/var/lib/corosync(/.*)? <br>
/usr/lib/heartbeat(/.*)? <br>
/var/lib/heartbeat(/.*)? <br>
/var/lib/pacemaker(/.*)?</p>


<p style="margin-left:11%; margin-top: 1em"><b>cluster_var_run_t</b></p>


<p style="margin-left:11%; margin-top: 1em">/var/run/crm(/.*)?
<br>
/var/run/cman_.* <br>
/var/run/rsctmp(/.*)? <br>
/var/run/aisexec.* <br>
/var/run/heartbeat(/.*)? <br>
/var/run/pcsd-ruby.socket <br>
/var/run/corosync-qnetd(/.*)? <br>
/var/run/corosync-qdevice(/.*)? <br>
/var/run/pcsd.socket <br>
/var/run/corosync.pid <br>
/var/run/cpglockd.pid <br>
/var/run/rgmanager.pid <br>
/var/run/cluster/rgmanager.sk</p>


<p style="margin-left:11%; margin-top: 1em"><b>fenced_lock_t</b></p>


<p style="margin-left:11%; margin-top: 1em">/var/lock/fence_manual.lock</p>


<p style="margin-left:11%; margin-top: 1em"><b>fenced_tmp_t</b></p>


<p style="margin-left:11%; margin-top: 1em"><b>fenced_tmpfs_t</b></p>


<p style="margin-left:11%; margin-top: 1em"><b>fenced_var_run_t</b></p>


<p style="margin-left:11%; margin-top: 1em">/var/run/fence.*
<br>
/var/run/cluster/fence_scsi.* <br>
/var/run/cluster/mpath.devices <br>
/var/run/cluster/fenced_override</p>


<p style="margin-left:11%; margin-top: 1em"><b>krb5_host_rcache_t</b></p>


<p style="margin-left:11%; margin-top: 1em">/var/tmp/krb5_0.rcache2
<br>
/var/cache/krb5rcache(/.*)? <br>
/var/tmp/nfs_0 <br>
/var/tmp/DNS_25 <br>
/var/tmp/host_0 <br>
/var/tmp/imap_0 <br>
/var/tmp/HTTP_23 <br>
/var/tmp/HTTP_48 <br>
/var/tmp/ldap_55 <br>
/var/tmp/ldap_487 <br>
/var/tmp/ldapmap1_0</p>


<p style="margin-left:11%; margin-top: 1em"><b>root_t</b></p>


<p style="margin-left:11%; margin-top: 1em">/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
<br>
/ <br>
/initrd</p>


<p style="margin-left:11%; margin-top: 1em"><b>snmpd_var_lib_t</b></p>


<p style="margin-left:11%; margin-top: 1em">/var/agentx(/.*)?
<br>
/var/net-snmp(/.*) <br>
/var/lib/snmp(/.*)? <br>
/var/net-snmp(/.*)? <br>
/var/lib/net-snmp(/.*)? <br>
/var/spool/snmptt(/.*)? <br>
/usr/share/snmp/mibs/.index</p>

<h2>FILE CONTEXTS
<a name="FILE CONTEXTS"></a>
</h2>


<p style="margin-left:11%; margin-top: 1em">SELinux
requires files to have an extended attribute to define the
file type.</p>

<p style="margin-left:11%; margin-top: 1em">You can see the
context of a file using the <b>&minus;Z</b> option to
<b>ls</b></p>

<p style="margin-left:11%; margin-top: 1em">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.</p>

<p style="margin-left:11%; margin-top: 1em"><b>STANDARD
FILE CONTEXT</b></p>

<p style="margin-left:11%; margin-top: 1em">SELinux defines
the file context types for the fenced, 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.</p>

<p style="margin-left:11%; margin-top: 1em"><b>semanage
fcontext -a -t fenced_tmp_t
&rsquo;/srv/myfenced_content(/.*)?&rsquo; <br>
restorecon -R -v /srv/myfenced_content</b></p>

<p style="margin-left:11%; margin-top: 1em">Note: SELinux
often uses regular expressions to specify labels that match
multiple files.</p>

<p style="margin-left:11%; margin-top: 1em"><i>The
following file types are defined for fenced:</i></p>


<p style="margin-left:11%; margin-top: 1em"><b>fenced_exec_t</b></p>

<p style="margin-left:11%; margin-top: 1em">- Set files
with the fenced_exec_t type, if you want to transition an
executable to the fenced_t domain. <br>
Paths:</p>

<p style="margin-left:18%;">/usr/sbin/fenced,
/usr/sbin/fence_node, /usr/sbin/fence_tool,
/usr/sbin/fence_virtd, /usr/sbin/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</p>


<p style="margin-left:11%; margin-top: 1em"><b>fenced_lock_t</b></p>

<p style="margin-left:11%; margin-top: 1em">- Set files
with the fenced_lock_t type, if you want to treat the files
as fenced lock data, stored under the /var/lock
directory</p>


<p style="margin-left:11%; margin-top: 1em"><b>fenced_tmp_t</b></p>

<p style="margin-left:11%; margin-top: 1em">- Set files
with the fenced_tmp_t type, if you want to store fenced
temporary files in the /tmp directories.</p>


<p style="margin-left:11%; margin-top: 1em"><b>fenced_tmpfs_t</b></p>

<p style="margin-left:11%; margin-top: 1em">- Set files
with the fenced_tmpfs_t type, if you want to store fenced
files on a tmpfs file system.</p>


<p style="margin-left:11%; margin-top: 1em"><b>fenced_var_log_t</b></p>

<p style="margin-left:11%; margin-top: 1em">- Set files
with the fenced_var_log_t type, if you want to treat the
data as fenced var log data, usually stored under the
/var/log directory.</p>


<p style="margin-left:11%; margin-top: 1em"><b>fenced_var_run_t</b></p>

<p style="margin-left:11%; margin-top: 1em">- Set files
with the fenced_var_run_t type, if you want to store the
fenced files under the /run or /var/run directory. <br>
Paths:</p>

<p style="margin-left:18%;">/var/run/fence.*,
/var/run/cluster/fence_scsi.*,
/var/run/cluster/mpath.devices,
/var/run/cluster/fenced_override</p>

<p style="margin-left:11%; margin-top: 1em">Note: File
context can be temporarily modified with the chcon command.
If you want to permanently change the file context you need
to use the <b>semanage fcontext</b> command. This will
modify the SELinux labeling database. You will need to use
<b>restorecon</b> to apply the labels.</p>

<h2>COMMANDS
<a name="COMMANDS"></a>
</h2>


<p style="margin-left:11%; margin-top: 1em"><b>semanage
fcontext</b> can also be used to manipulate default file
context mappings.</p>

<p style="margin-left:11%; margin-top: 1em"><b>semanage
permissive</b> can also be used to manipulate whether or not
a process type is permissive.</p>

<p style="margin-left:11%; margin-top: 1em"><b>semanage
module</b> can also be used to enable/disable/install/remove
policy modules.</p>

<p style="margin-left:11%; margin-top: 1em"><b>semanage
boolean</b> can also be used to manipulate the booleans</p>


<p style="margin-left:11%; margin-top: 1em"><b>system-config-selinux</b>
is a GUI tool available to customize SELinux policy
settings.</p>

<h2>AUTHOR
<a name="AUTHOR"></a>
</h2>


<p style="margin-left:11%; margin-top: 1em">This manual
page was auto-generated using <b>sepolicy manpage .</b></p>

<h2>SEE ALSO
<a name="SEE ALSO"></a>
</h2>


<p style="margin-left:11%; margin-top: 1em">selinux(8),
fenced(8), semanage(8), restorecon(8), chcon(1),
sepolicy(8), setsebool(8)</p>
<hr>
</body>
</html>