Current File : //proc/self/root/kunden/usr/share/selinux/devel/html/greylist_milter.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>greylist_milter_selinux</title>

</head>
<body>

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

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



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

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

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


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

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


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

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


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

<p style="margin-left:11%; margin-top: 1em">Note:
<b>semanage permissive -a greylist_milter_t</b> can be used
to make the process type greylist_milter_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.
greylist_milter policy is extremely flexible and has several
booleans that allow you to manipulate the policy and run
greylist_milter 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>

<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 greylist_milter_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_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>greylist_milter_data_t</b></p>


<p style="margin-left:11%; margin-top: 1em">/var/lib/sqlgrey(/.*)?
<br>
/var/lib/milter-greylist(/.*)? <br>
/var/run/milter-greylist(/.*)? <br>
/var/run/sqlgrey.pid <br>
/var/run/milter-greylist.pid</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>

<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
greylist_milter policy is very flexible allowing users to
setup their greylist_milter 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">greylist_milter
policy stores data with multiple different file context
types under the /var/run/milter-greylist 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/run/milter-greylist /srv/milter-greylist
<br>
restorecon -R -v /srv/milter-greylist</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 greylist_milter, 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 greylist_milter_data_t
&rsquo;/srv/mygreylist_milter_content(/.*)?&rsquo; <br>
restorecon -R -v /srv/mygreylist_milter_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
greylist_milter:</i></p>


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

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

<p style="margin-left:18%;">/var/lib/sqlgrey(/.*)?,
/var/lib/milter-greylist(/.*)?,
/var/run/milter-greylist(/.*)?, /var/run/sqlgrey.pid,
/var/run/milter-greylist.pid</p>


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

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

<p style="margin-left:18%;">/usr/sbin/sqlgrey,
/usr/sbin/milter-greylist</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),
greylist_milter(8), semanage(8), restorecon(8), chcon(1),
sepolicy(8), setsebool(8)</p>
<hr>
</body>
</html>