1spamass_milter_selinux(8)SELinux Policy spamass_milterspamass_milter_selinux(8)
2
6 spamass_milter_selinux - Security Enhanced Linux Policy for the spa‐
7 mass_milter processes
8
10 Security-Enhanced Linux secures the spamass_milter processes via flexi‐
11 ble mandatory access control.
12 The spamass_milter processes execute with the spamass_milter_t SELinux
14 type. You can check if you have these processes running by executing
15 the ps command with the -Z qualifier.
16 For example:
18 ps -eZ | grep spamass_milter_t
20
24 The spamass_milter_t SELinux type can be entered via the spamass_mil‐
25 ter_exec_t file type.
26 The default entrypoint paths for the spamass_milter_t domain are the
28 following:
29 /usr/sbin/spamass-milter
31
33 SELinux defines process types (domains) for each process running on the
34 system
35 You can see the context of a process using the -Z option to ps
37 Policy governs the access confined processes have to files. SELinux
39 spamass_milter policy is very flexible allowing users to setup their
40 spamass_milter processes in as secure a method as possible.
41 The following process types are defined for spamass_milter:
43 spamass_milter_t
45 Note: semanage permissive -a spamass_milter_t can be used to make the
47 process type spamass_milter_t permissive. SELinux does not deny access
48 to permissive process types, but the AVC (SELinux denials) messages are
49 still generated.
50
53 SELinux policy is customizable based on least access required. spa‐
54 mass_milter policy is extremely flexible and has several booleans that
55 allow you to manipulate the policy and run spamass_milter with the
56 tightest access possible.
57 If you want to allow all domains to execute in fips_mode, you must turn
61 on the fips_mode boolean. Enabled by default.
62 setsebool -P fips_mode 1
64
68 The SELinux process type spamass_milter_t can manage files labeled with
69 the following file types. The paths listed are the default paths for
70 these file types. Note the processes UID still need to have DAC per‐
71 missions.
72 cluster_conf_t
74 /etc/cluster(/.*)?
76 cluster_var_lib_t
78 /var/lib/pcsd(/.*)?
80 /var/lib/cluster(/.*)?
81 /var/lib/openais(/.*)?
82 /var/lib/pengine(/.*)?
83 /var/lib/corosync(/.*)?
84 /usr/lib/heartbeat(/.*)?
85 /var/lib/heartbeat(/.*)?
86 /var/lib/pacemaker(/.*)?
87 cluster_var_run_t
89 /var/run/crm(/.*)?
91 /var/run/cman_.*
92 /var/run/rsctmp(/.*)?
93 /var/run/aisexec.*
94 /var/run/heartbeat(/.*)?
95 /var/run/corosync-qnetd(/.*)?
96 /var/run/corosync-qdevice(/.*)?
97 /var/run/corosync.pid
98 /var/run/cpglockd.pid
99 /var/run/rgmanager.pid
100 /var/run/cluster/rgmanager.sk
101 root_t
103 /sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
105 /
106 /initrd
107 spamass_milter_data_t
109 /var/run/spamass(/.*)?
111 /var/run/spamass-milter(/.*)?
112 /var/spool/postfix/spamass(/.*)?
113 /var/run/spamass-milter.pid
114
117 SELinux requires files to have an extended attribute to define the file
118 type.
119 You can see the context of a file using the -Z option to ls
121 Policy governs the access confined processes have to these files.
123 SELinux spamass_milter policy is very flexible allowing users to setup
124 their spamass_milter processes in as secure a method as possible.
125 EQUIVALENCE DIRECTORIES
127 spamass_milter policy stores data with multiple different file context
130 types under the /var/run/spamass directory. If you would like to store
131 the data in a different directory you can use the semanage command to
132 create an equivalence mapping. If you wanted to store this data under
133 the /srv directory you would execute the following command:
134 semanage fcontext -a -e /var/run/spamass /srv/spamass
136 restorecon -R -v /srv/spamass
137 STANDARD FILE CONTEXT
139 SELinux defines the file context types for the spamass_milter, if you
141 wanted to store files with these types in a diffent paths, you need to
142 execute the semanage command to sepecify alternate labeling and then
143 use restorecon to put the labels on disk.
144 semanage fcontext -a -t spamass_milter_state_t '/srv/myspamass_mil‐
146 ter_content(/.*)?'
147 restorecon -R -v /srv/myspamass_milter_content
148 Note: SELinux often uses regular expressions to specify labels that
150 match multiple files.
151 The following file types are defined for spamass_milter:
153 spamass_milter_data_t
157 - Set files with the spamass_milter_data_t type, if you want to treat
159 the files as spamass milter content.
160 Paths:
163 /var/run/spamass(/.*)?, /var/run/spamass-milter(/.*)?,
164 /var/spool/postfix/spamass(/.*)?, /var/run/spamass-milter.pid
165 spamass_milter_exec_t
168 - Set files with the spamass_milter_exec_t type, if you want to transi‐
170 tion an executable to the spamass_milter_t domain.
171 spamass_milter_state_t
175 - Set files with the spamass_milter_state_t type, if you want to treat
177 the files as spamass milter state data.
178 Note: File context can be temporarily modified with the chcon command.
182 If you want to permanently change the file context you need to use the
183 semanage fcontext command. This will modify the SELinux labeling data‐
184 base. You will need to use restorecon to apply the labels.
185
188 semanage fcontext can also be used to manipulate default file context
189 mappings.
190 semanage permissive can also be used to manipulate whether or not a
192 process type is permissive.
193 semanage module can also be used to enable/disable/install/remove pol‐
195 icy modules.
196 semanage boolean can also be used to manipulate the booleans
198 system-config-selinux is a GUI tool available to customize SELinux pol‐
201 icy settings.
202
205 This manual page was auto-generated using sepolicy manpage .
206
209 selinux(8), spamass_milter(8), semanage(8), restorecon(8), chcon(1),
210 sepolicy(8), setsebool(8)
211spamass_milter 20-05-05 spamass_milter_selinux(8)