Current File : //kunden/usr/share/selinux/devel/html/dirsrv.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>dirsrv_selinux</title>

</head>
<body>

<h1 align="center">dirsrv_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">dirsrv_selinux
&minus; Security Enhanced Linux Policy for the dirsrv
processes</p>

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



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

<p style="margin-left:11%; margin-top: 1em">The dirsrv
processes execute with the dirsrv_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 dirsrv_t</b></p>

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


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

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


<p style="margin-left:11%; margin-top: 1em">/usr/sbin/ns-slapd</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 dirsrv
policy is very flexible allowing users to setup their dirsrv
processes in as secure a method as possible.</p>

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

<p style="margin-left:11%; margin-top: 1em"><b>dirsrv_t,
dirsrv_snmp_t, dirsrvadmin_t,
dirsrvadmin_unconfined_script_t,
dirsrvadmin_script_t</b></p>

<p style="margin-left:11%; margin-top: 1em">Note:
<b>semanage permissive -a dirsrv_t</b> can be used to make
the process type dirsrv_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. dirsrv
policy is extremely flexible and has several booleans that
allow you to manipulate the policy and run dirsrv 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 confined applications to run with kerberos, you must
turn on the kerberos_enabled boolean. Enabled by
default.</p>

<p style="margin-left:11%; margin-top: 1em"><b>setsebool -P
kerberos_enabled 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 dirsrv_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>dirsrv_config_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>/etc/dirsrv(/.*)?</p></td></tr>
</table>


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


<p style="margin-left:11%; margin-top: 1em"><b>dirsrv_tmpfs_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>/dev/shm/slapd-.*</p></td></tr>
</table>


<p style="margin-left:11%; margin-top: 1em"><b>dirsrv_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/dirsrv(/.*)?</p></td></tr>
</table>


<p style="margin-left:11%; margin-top: 1em"><b>dirsrv_var_lock_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/lock/dirsrv(/.*)?</p></td></tr>
</table>


<p style="margin-left:11%; margin-top: 1em"><b>dirsrv_var_log_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/log/dirsrv(/.*)?</p></td></tr>
</table>


<p style="margin-left:11%; margin-top: 1em"><b>dirsrv_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/slapd.*</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">


<p>/var/run/dirsrv(/.*)?</p></td></tr>
</table>


<p style="margin-left:11%; margin-top: 1em"><b>faillog_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/log/btmp.*</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">


<p>/var/log/faillog.*</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">


<p>/var/log/tallylog.*</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">


<p>/var/run/faillock(/.*)?</p></td></tr>
</table>


<p style="margin-left:11%; margin-top: 1em"><b>krb5_host_rcache_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/tmp/krb5_0.rcache2</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">


<p>/var/cache/krb5rcache(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">


<p>/var/tmp/nfs_0</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">


<p>/var/tmp/DNS_25</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">


<p>/var/tmp/host_0</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">


<p>/var/tmp/imap_0</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">


<p>/var/tmp/HTTP_23</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">


<p>/var/tmp/HTTP_48</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">


<p>/var/tmp/ldap_55</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">


<p>/var/tmp/ldap_487</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">


<p>/var/tmp/ldapmap1_0</p></td></tr>
</table>


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


<p style="margin-left:11%; margin-top: 1em"><b>security_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>/selinux</p></td></tr>
</table>


<p style="margin-left:11%; margin-top: 1em"><b>systemd_passwd_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/systemd/ask-password(/.*)?</p></td></tr>
<tr valign="top" align="left">
<td width="8%"></td>
<td width="92%">


<p>/var/run/systemd/ask-password-block(/.*)?</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>&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
dirsrv policy is very flexible allowing users to setup their
dirsrv processes in as secure a method as possible.</p>

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

<p style="margin-left:11%; margin-top: 1em">dirsrv policy
stores data with multiple different file context types under
the /var/log/dirsrv directory. If you would like to store
the data in a different directory you can use the semanage
command to create an equivalence mapping. If you wanted to
store this data under the /srv directory you would execute
the following command:</p>

<p style="margin-left:11%; margin-top: 1em"><b>semanage
fcontext -a -e /var/log/dirsrv /srv/dirsrv <br>
restorecon -R -v /srv/dirsrv</b></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 dirsrv, 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 dirsrvadmin_ra_content_t
&rsquo;/srv/mydirsrv_content(/.*)?&rsquo; <br>
restorecon -R -v /srv/mydirsrv_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 dirsrv:</i></p>


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

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


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

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


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

<p style="margin-left:11%; margin-top: 1em">- Set files
with the dirsrv_share_t type, if you want to treat the files
as dirsrv share data.</p>


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

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

<p style="margin-left:18%;">/usr/sbin/ldap-agent,
/usr/sbin/ldap-agent-bin</p>


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

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


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

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


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

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


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

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


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

<p style="margin-left:11%; margin-top: 1em">- Set files
with the dirsrv_unit_file_t type, if you want to treat the
files as dirsrv unit content.</p>


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

<p style="margin-left:11%; margin-top: 1em">- Set files
with the dirsrv_var_lib_t type, if you want to store the
dirsrv files under the /var/lib directory.</p>


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

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


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

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


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

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

<p style="margin-left:18%;">/var/run/slapd.*,
/var/run/dirsrv(/.*)?</p>


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

<p style="margin-left:11%; margin-top: 1em">- Set files
with the dirsrvadmin_config_t type, if you want to treat the
files as dirsrvadmin configuration data, usually stored
under the /etc directory. <br>
Paths:</p>

<p style="margin-left:18%;">/etc/dirsrv/dsgw(/.*)?,
/etc/dirsrv/admin-serv(/.*)?</p>


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

<p style="margin-left:11%; margin-top: 1em">- Set files
with the dirsrvadmin_content_t type, if you want to treat
the files as dirsrvadmin content.</p>


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

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

<p style="margin-left:18%;">/usr/sbin/stop-ds-admin,
/usr/sbin/start-ds-admin, /usr/sbin/restart-ds-admin</p>


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

<p style="margin-left:11%; margin-top: 1em">- Set files
with the dirsrvadmin_htaccess_t type, if you want to treat
the file as a dirsrvadmin access file.</p>


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

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


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

<p style="margin-left:11%; margin-top: 1em">- Set files
with the dirsrvadmin_ra_content_t type, if you want to treat
the files as dirsrvadmin read/append content.</p>


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

<p style="margin-left:11%; margin-top: 1em">- Set files
with the dirsrvadmin_rw_content_t type, if you want to treat
the files as dirsrvadmin read/write content.</p>


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

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

<p style="margin-left:18%;">/usr/lib/dirsrv/cgi-bin(/.*)?,
/usr/lib/dirsrv/dsgw-cgi-bin(/.*)?</p>


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

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


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

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


<p style="margin-left:18%;">/usr/lib/dirsrv/cgi-bin/ds_create,
/usr/lib/dirsrv/cgi-bin/ds_remove</p>


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

<p style="margin-left:11%; margin-top: 1em">- Set files
with the dirsrvadmin_unit_file_t type, if you want to treat
the files as dirsrvadmin unit content.</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),
dirsrv(8), semanage(8), restorecon(8), chcon(1),
sepolicy(8), setsebool(8), dirsrv_snmp_selinux(8),
dirsrv_snmp_selinux(8)</p>
<hr>
</body>
</html>