1greylist_milter_selinux(8S)ELinux Policy greylist_miltegrreylist_milter_selinux(8)
2
3
4
6 greylist_milter_selinux - Security Enhanced Linux Policy for the
7 greylist_milter processes
8
10 Security-Enhanced Linux secures the greylist_milter processes via flex‐
11 ible mandatory access control.
12
13 The greylist_milter processes execute with the greylist_milter_t
14 SELinux type. You can check if you have these processes running by exe‐
15 cuting the ps command with the -Z qualifier.
16
17 For example:
18
19 ps -eZ | grep greylist_milter_t
20
21
22
24 The greylist_milter_t SELinux type can be entered via the greylist_mil‐
25 ter_exec_t file type.
26
27 The default entrypoint paths for the greylist_milter_t domain are the
28 following:
29
30 /usr/sbin/sqlgrey, /usr/sbin/milter-greylist
31
33 SELinux defines process types (domains) for each process running on the
34 system
35
36 You can see the context of a process using the -Z option to ps
37
38 Policy governs the access confined processes have to files. SELinux
39 greylist_milter policy is very flexible allowing users to setup their
40 greylist_milter processes in as secure a method as possible.
41
42 The following process types are defined for greylist_milter:
43
44 greylist_milter_t
45
46 Note: semanage permissive -a greylist_milter_t can be used to make the
47 process type greylist_milter_t permissive. SELinux does not deny access
48 to permissive process types, but the AVC (SELinux denials) messages are
49 still generated.
50
51
53 SELinux policy is customizable based on least access required.
54 greylist_milter policy is extremely flexible and has several booleans
55 that allow you to manipulate the policy and run greylist_milter with
56 the tightest access possible.
57
58
59
60 If you want to allow users to resolve user passwd entries directly from
61 ldap rather then using a sssd server, you must turn on the authlo‐
62 gin_nsswitch_use_ldap boolean. Disabled by default.
63
64 setsebool -P authlogin_nsswitch_use_ldap 1
65
66
67
68 If you want to allow all daemons to write corefiles to /, you must turn
69 on the daemons_dump_core boolean. Disabled by default.
70
71 setsebool -P daemons_dump_core 1
72
73
74
75 If you want to enable cluster mode for daemons, you must turn on the
76 daemons_enable_cluster_mode boolean. Enabled by default.
77
78 setsebool -P daemons_enable_cluster_mode 1
79
80
81
82 If you want to allow all daemons to use tcp wrappers, you must turn on
83 the daemons_use_tcp_wrapper boolean. Disabled by default.
84
85 setsebool -P daemons_use_tcp_wrapper 1
86
87
88
89 If you want to allow all daemons the ability to read/write terminals,
90 you must turn on the daemons_use_tty boolean. Disabled by default.
91
92 setsebool -P daemons_use_tty 1
93
94
95
96 If you want to deny any process from ptracing or debugging any other
97 processes, you must turn on the deny_ptrace boolean. Enabled by
98 default.
99
100 setsebool -P deny_ptrace 1
101
102
103
104 If you want to allow any process to mmap any file on system with
105 attribute file_type, you must turn on the domain_can_mmap_files bool‐
106 ean. Enabled by default.
107
108 setsebool -P domain_can_mmap_files 1
109
110
111
112 If you want to allow all domains write to kmsg_device, while kernel is
113 executed with systemd.log_target=kmsg parameter, you must turn on the
114 domain_can_write_kmsg boolean. Disabled by default.
115
116 setsebool -P domain_can_write_kmsg 1
117
118
119
120 If you want to allow all domains to use other domains file descriptors,
121 you must turn on the domain_fd_use boolean. Enabled by default.
122
123 setsebool -P domain_fd_use 1
124
125
126
127 If you want to allow all domains to have the kernel load modules, you
128 must turn on the domain_kernel_load_modules boolean. Disabled by
129 default.
130
131 setsebool -P domain_kernel_load_modules 1
132
133
134
135 If you want to allow all domains to execute in fips_mode, you must turn
136 on the fips_mode boolean. Enabled by default.
137
138 setsebool -P fips_mode 1
139
140
141
142 If you want to enable reading of urandom for all domains, you must turn
143 on the global_ssp boolean. Disabled by default.
144
145 setsebool -P global_ssp 1
146
147
148
149 If you want to allow confined applications to run with kerberos, you
150 must turn on the kerberos_enabled boolean. Enabled by default.
151
152 setsebool -P kerberos_enabled 1
153
154
155
156 If you want to allow system to run with NIS, you must turn on the
157 nis_enabled boolean. Disabled by default.
158
159 setsebool -P nis_enabled 1
160
161
162
163 If you want to allow confined applications to use nscd shared memory,
164 you must turn on the nscd_use_shm boolean. Disabled by default.
165
166 setsebool -P nscd_use_shm 1
167
168
169
171 The SELinux process type greylist_milter_t can manage files labeled
172 with the following file types. The paths listed are the default paths
173 for these file types. Note the processes UID still need to have DAC
174 permissions.
175
176 cluster_conf_t
177
178 /etc/cluster(/.*)?
179
180 cluster_var_lib_t
181
182 /var/lib/pcsd(/.*)?
183 /var/lib/cluster(/.*)?
184 /var/lib/openais(/.*)?
185 /var/lib/pengine(/.*)?
186 /var/lib/corosync(/.*)?
187 /usr/lib/heartbeat(/.*)?
188 /var/lib/heartbeat(/.*)?
189 /var/lib/pacemaker(/.*)?
190
191 cluster_var_run_t
192
193 /var/run/crm(/.*)?
194 /var/run/cman_.*
195 /var/run/rsctmp(/.*)?
196 /var/run/aisexec.*
197 /var/run/heartbeat(/.*)?
198 /var/run/corosync-qnetd(/.*)?
199 /var/run/corosync-qdevice(/.*)?
200 /var/run/cpglockd.pid
201 /var/run/corosync.pid
202 /var/run/rgmanager.pid
203 /var/run/cluster/rgmanager.sk
204
205 greylist_milter_data_t
206
207 /var/lib/sqlgrey(/.*)?
208 /var/lib/milter-greylist(/.*)?
209 /var/run/milter-greylist(/.*)?
210 /var/run/sqlgrey.pid
211 /var/run/milter-greylist.pid
212
213 root_t
214
215 /sysroot/ostree/deploy/.*-atomic.*/deploy(/.*)?
216 /
217 /initrd
218
219
221 SELinux requires files to have an extended attribute to define the file
222 type.
223
224 You can see the context of a file using the -Z option to ls
225
226 Policy governs the access confined processes have to these files.
227 SELinux greylist_milter policy is very flexible allowing users to setup
228 their greylist_milter processes in as secure a method as possible.
229
230 EQUIVALENCE DIRECTORIES
231
232
233 greylist_milter policy stores data with multiple different file context
234 types under the /var/run/milter-greylist directory. If you would like
235 to store the data in a different directory you can use the semanage
236 command to create an equivalence mapping. If you wanted to store this
237 data under the /srv dirctory you would execute the following command:
238
239 semanage fcontext -a -e /var/run/milter-greylist /srv/milter-greylist
240 restorecon -R -v /srv/milter-greylist
241
242 STANDARD FILE CONTEXT
243
244 SELinux defines the file context types for the greylist_milter, if you
245 wanted to store files with these types in a diffent paths, you need to
246 execute the semanage command to sepecify alternate labeling and then
247 use restorecon to put the labels on disk.
248
249 semanage fcontext -a -t greylist_milter_data_t '/srv/mygreylist_mil‐
250 ter_content(/.*)?'
251 restorecon -R -v /srv/mygreylist_milter_content
252
253 Note: SELinux often uses regular expressions to specify labels that
254 match multiple files.
255
256 The following file types are defined for greylist_milter:
257
258
259
260 greylist_milter_data_t
261
262 - Set files with the greylist_milter_data_t type, if you want to treat
263 the files as greylist milter content.
264
265
266 Paths:
267 /var/lib/sqlgrey(/.*)?, /var/lib/milter-greylist(/.*)?,
268 /var/run/milter-greylist(/.*)?, /var/run/sqlgrey.pid,
269 /var/run/milter-greylist.pid
270
271
272 greylist_milter_exec_t
273
274 - Set files with the greylist_milter_exec_t type, if you want to tran‐
275 sition an executable to the greylist_milter_t domain.
276
277
278 Paths:
279 /usr/sbin/sqlgrey, /usr/sbin/milter-greylist
280
281
282 Note: File context can be temporarily modified with the chcon command.
283 If you want to permanently change the file context you need to use the
284 semanage fcontext command. This will modify the SELinux labeling data‐
285 base. You will need to use restorecon to apply the labels.
286
287
289 semanage fcontext can also be used to manipulate default file context
290 mappings.
291
292 semanage permissive can also be used to manipulate whether or not a
293 process type is permissive.
294
295 semanage module can also be used to enable/disable/install/remove pol‐
296 icy modules.
297
298 semanage boolean can also be used to manipulate the booleans
299
300
301 system-config-selinux is a GUI tool available to customize SELinux pol‐
302 icy settings.
303
304
306 This manual page was auto-generated using sepolicy manpage .
307
308
310 selinux(8), greylist_milter(8), semanage(8), restorecon(8), chcon(1),
311 sepolicy(8) , setsebool(8)
312
313
314
315greylist_milter 19-04-25 greylist_milter_selinux(8)