| Current File : //proc/self/root/kunden/usr/share/selinux/devel/html/NetworkManager_dispatcher.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>NetworkManager_dispatcher_selinux</title>
</head>
<body>
<h1 align="center">NetworkManager_dispatcher_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">NetworkManager_dispatcher_selinux
− Security Enhanced Linux Policy for the
NetworkManager_dispatcher processes</p>
<h2>DESCRIPTION
<a name="DESCRIPTION"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">Security-Enhanced
Linux secures the NetworkManager_dispatcher processes via
flexible mandatory access control.</p>
<p style="margin-left:11%; margin-top: 1em">The
NetworkManager_dispatcher processes execute with the
NetworkManager_dispatcher_t SELinux type. You can check if
you have these processes running by executing the <b>ps</b>
command with the <b>−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 NetworkManager_dispatcher_t</b></p>
<h2>ENTRYPOINTS
<a name="ENTRYPOINTS"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">The
NetworkManager_dispatcher_t SELinux type can be entered via
the <b>NetworkManager_dispatcher_exec_t</b> file type.</p>
<p style="margin-left:11%; margin-top: 1em">The default
entrypoint paths for the NetworkManager_dispatcher_t domain
are the following:</p>
<p style="margin-left:11%; margin-top: 1em">/usr/libexec/nm-dispatcher</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>−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
NetworkManager_dispatcher policy is very flexible allowing
users to setup their NetworkManager_dispatcher processes in
as secure a method as possible.</p>
<p style="margin-left:11%; margin-top: 1em">The following
process types are defined for NetworkManager_dispatcher:</p>
<p style="margin-left:11%; margin-top: 1em"><b>NetworkManager_dispatcher_t,
NetworkManager_dispatcher_custom_t,
NetworkManager_dispatcher_chronyc_t,
NetworkManager_dispatcher_cloud_t,
NetworkManager_dispatcher_console_t,
NetworkManager_dispatcher_ddclient_t,
NetworkManager_dispatcher_dhclient_t,
NetworkManager_dispatcher_dnssec_t,
NetworkManager_dispatcher_iscsid_t,
NetworkManager_dispatcher_sendmail_t,
NetworkManager_dispatcher_tlp_t,
NetworkManager_dispatcher_winbind_t</b></p>
<p style="margin-left:11%; margin-top: 1em">Note:
<b>semanage permissive -a NetworkManager_dispatcher_t</b>
can be used to make the process type
NetworkManager_dispatcher_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.
NetworkManager_dispatcher policy is extremely flexible and
has several booleans that allow you to manipulate the policy
and run NetworkManager_dispatcher with the tightest access
possible.</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>
<h2>MANAGED FILES
<a name="MANAGED FILES"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">The SELinux
process type NetworkManager_dispatcher_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>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="8%"></td>
<td width="7%"></td>
<td width="85%">
<p>/etc/cluster(/.*)?</p></td></tr>
</table>
<p style="margin-left:11%; margin-top: 1em"><b>cluster_var_lib_t</b></p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/lib/pcsd(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/lib/cluster(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/lib/openais(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/lib/pengine(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/lib/corosync(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/usr/lib/heartbeat(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/lib/heartbeat(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/lib/pacemaker(/.*)?</p></td></tr>
</table>
<p style="margin-left:11%; margin-top: 1em"><b>cluster_var_run_t</b></p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/run/crm(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/run/cman_.*</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/run/rsctmp(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/run/aisexec.*</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/run/heartbeat(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/run/pcsd-ruby.socket</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/run/corosync-qnetd(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/run/corosync-qdevice(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/run/pcsd.socket</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/run/corosync.pid</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/run/cpglockd.pid</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/run/rgmanager.pid</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/var/run/cluster/rgmanager.sk</p></td></tr>
</table>
<p style="margin-left:11%; margin-top: 1em"><b>root_t</b></p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">
<p>/initrd</p></td></tr>
</table>
<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>−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
NetworkManager_dispatcher policy is very flexible allowing
users to setup their NetworkManager_dispatcher 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 NetworkManager_dispatcher, 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 NetworkManager_dispatcher_console_var_run_t
’/srv/myNetworkManager_dispatcher_content(/.*)?’
<br>
restorecon -R -v
/srv/myNetworkManager_dispatcher_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
NetworkManager_dispatcher:</i></p>
<p style="margin-left:11%; margin-top: 1em"><b>NetworkManager_dispatcher_chronyc_script_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the NetworkManager_dispatcher_chronyc_script_t type, if
you want to treat the files as NetworkManager dispatcher
chronyc script data. <br>
Paths:</p>
<p style="margin-left:18%;">/etc/NetworkManager/dispatcher.d/20-chrony-dhcp,
/usr/lib/NetworkManager/dispatcher.d/20-chrony-dhcp,
/etc/NetworkManager/dispatcher.d/20-chrony-onoffline,
/usr/lib/NetworkManager/dispatcher.d/20-chrony-onoffline</p>
<p style="margin-left:11%; margin-top: 1em"><b>NetworkManager_dispatcher_cloud_script_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the NetworkManager_dispatcher_cloud_script_t type, if
you want to treat the files as NetworkManager dispatcher
cloud script data. <br>
Paths:</p>
<p style="margin-left:18%;">/etc/NetworkManager/dispatcher.d/hook-network-manager,
/etc/NetworkManager/dispatcher.d/cloud-init-azure-hook,
/usr/lib/NetworkManager/dispatcher.d/90-nm-cloud-setup.sh,
/usr/lib/NetworkManager/dispatcher.d/no-wait.d/90-nm-cloud-setup.sh</p>
<p style="margin-left:11%; margin-top: 1em"><b>NetworkManager_dispatcher_console_script_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the NetworkManager_dispatcher_console_script_t type, if
you want to treat the files as NetworkManager dispatcher
console script data.</p>
<p style="margin-left:11%; margin-top: 1em"><b>NetworkManager_dispatcher_console_var_run_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the NetworkManager_dispatcher_console_var_run_t type,
if you want to store the NetworkManager dispatcher console
files under the /run or /var/run directory.</p>
<p style="margin-left:11%; margin-top: 1em"><b>NetworkManager_dispatcher_ddclient_script_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the NetworkManager_dispatcher_ddclient_script_t type,
if you want to treat the files as NetworkManager dispatcher
ddclient script data.</p>
<p style="margin-left:11%; margin-top: 1em"><b>NetworkManager_dispatcher_dhclient_script_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the NetworkManager_dispatcher_dhclient_script_t type,
if you want to treat the files as NetworkManager dispatcher
dhclient script data. <br>
Paths:</p>
<p style="margin-left:18%;">/etc/NetworkManager/dispatcher.d/11-dhclient,
/usr/lib/NetworkManager/dispatcher.d/11-dhclient</p>
<p style="margin-left:11%; margin-top: 1em"><b>NetworkManager_dispatcher_dnssec_script_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the NetworkManager_dispatcher_dnssec_script_t type, if
you want to treat the files as NetworkManager dispatcher
dnssec script data.</p>
<p style="margin-left:11%; margin-top: 1em"><b>NetworkManager_dispatcher_exec_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the NetworkManager_dispatcher_exec_t type, if you want
to transition an executable to the
NetworkManager_dispatcher_t domain.</p>
<p style="margin-left:11%; margin-top: 1em"><b>NetworkManager_dispatcher_iscsid_script_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the NetworkManager_dispatcher_iscsid_script_t type, if
you want to treat the files as NetworkManager dispatcher
iscsid script data.</p>
<p style="margin-left:11%; margin-top: 1em"><b>NetworkManager_dispatcher_script_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the NetworkManager_dispatcher_script_t type, if you
want to treat the files as NetworkManager dispatcher script
data. <br>
Paths:</p>
<p style="margin-left:18%;">/etc/NetworkManager/dispatcher.d(/.*)?,
/usr/lib/NetworkManager/dispatcher.d(/.*)?</p>
<p style="margin-left:11%; margin-top: 1em"><b>NetworkManager_dispatcher_sendmail_script_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the NetworkManager_dispatcher_sendmail_script_t type,
if you want to treat the files as NetworkManager dispatcher
sendmail script data.</p>
<p style="margin-left:11%; margin-top: 1em"><b>NetworkManager_dispatcher_tlp_script_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the NetworkManager_dispatcher_tlp_script_t type, if you
want to treat the files as NetworkManager dispatcher tlp
script data.</p>
<p style="margin-left:11%; margin-top: 1em"><b>NetworkManager_dispatcher_winbind_script_t</b></p>
<p style="margin-left:11%; margin-top: 1em">- Set files
with the NetworkManager_dispatcher_winbind_script_t type, if
you want to treat the files as NetworkManager dispatcher
winbind script data.</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),
NetworkManager_dispatcher(8), semanage(8), restorecon(8),
chcon(1), sepolicy(8), setsebool(8),
NetworkManager_dispatcher_chronyc_selinux(8),
NetworkManager_dispatcher_chronyc_selinux(8),
NetworkManager_dispatcher_cloud_selinux(8),
NetworkManager_dispatcher_cloud_selinux(8),
NetworkManager_dispatcher_console_selinux(8),
NetworkManager_dispatcher_console_selinux(8),
NetworkManager_dispatcher_custom_selinux(8),
NetworkManager_dispatcher_custom_selinux(8),
NetworkManager_dispatcher_ddclient_selinux(8),
NetworkManager_dispatcher_ddclient_selinux(8),
NetworkManager_dispatcher_dhclient_selinux(8),
NetworkManager_dispatcher_dhclient_selinux(8),
NetworkManager_dispatcher_dnssec_selinux(8),
NetworkManager_dispatcher_dnssec_selinux(8),
NetworkManager_dispatcher_iscsid_selinux(8),
NetworkManager_dispatcher_iscsid_selinux(8),
NetworkManager_dispatcher_sendmail_selinux(8),
NetworkManager_dispatcher_sendmail_selinux(8),
NetworkManager_dispatcher_tlp_selinux(8),
NetworkManager_dispatcher_tlp_selinux(8),
NetworkManager_dispatcher_winbind_selinux(8),
NetworkManager_dispatcher_winbind_selinux(8)</p>
<hr>
</body>
</html>