1postgrey_selinux(8)         SELinux Policy postgrey        postgrey_selinux(8)
2
3
4

NAME

6       postgrey_selinux - Security Enhanced Linux Policy for the postgrey pro‐
7       cesses
8

DESCRIPTION

10       Security-Enhanced Linux secures the  postgrey  processes  via  flexible
11       mandatory access control.
12
13       The  postgrey  processes  execute with the postgrey_t SELinux type. You
14       can check if you have these processes running by executing the ps  com‐
15       mand with the -Z qualifier.
16
17       For example:
18
19       ps -eZ | grep postgrey_t
20
21
22

ENTRYPOINTS

24       The postgrey_t SELinux type can be entered via the postgrey_exec_t file
25       type.
26
27       The default entrypoint paths for the postgrey_t domain are the  follow‐
28       ing:
29
30       /usr/sbin/postgrey
31

PROCESS TYPES

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       postgrey policy is very flexible allowing users to setup their postgrey
40       processes in as secure a method as possible.
41
42       The following process types are defined for postgrey:
43
44       postgrey_t
45
46       Note: semanage permissive -a postgrey_t can be used to make the process
47       type  postgrey_t permissive. SELinux does not deny access to permissive
48       process types, but the AVC (SELinux denials) messages are still  gener‐
49       ated.
50
51

BOOLEANS

53       SELinux  policy  is customizable based on least access required.  post‐
54       grey policy is extremely flexible and has several booleans  that  allow
55       you  to manipulate the policy and run postgrey with the tightest access
56       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

PORT TYPES

171       SELinux defines port types to represent TCP and UDP ports.
172
173       You can see the types associated with a port  by  using  the  following
174       command:
175
176       semanage port -l
177
178
179       Policy  governs  the  access  confined  processes  have to these ports.
180       SELinux postgrey policy is very flexible allowing users to setup  their
181       postgrey processes in as secure a method as possible.
182
183       The following port types are defined for postgrey:
184
185
186       postgrey_port_t
187
188
189
190       Default Defined Ports:
191                 tcp 60000
192

MANAGED FILES

194       The  SELinux  process type postgrey_t can manage files labeled with the
195       following file types.  The paths listed are the default paths for these
196       file types.  Note the processes UID still need to have DAC permissions.
197
198       cluster_conf_t
199
200            /etc/cluster(/.*)?
201
202       cluster_var_lib_t
203
204            /var/lib/pcsd(/.*)?
205            /var/lib/cluster(/.*)?
206            /var/lib/openais(/.*)?
207            /var/lib/pengine(/.*)?
208            /var/lib/corosync(/.*)?
209            /usr/lib/heartbeat(/.*)?
210            /var/lib/heartbeat(/.*)?
211            /var/lib/pacemaker(/.*)?
212
213       cluster_var_run_t
214
215            /var/run/crm(/.*)?
216            /var/run/cman_.*
217            /var/run/rsctmp(/.*)?
218            /var/run/aisexec.*
219            /var/run/heartbeat(/.*)?
220            /var/run/corosync-qnetd(/.*)?
221            /var/run/corosync-qdevice(/.*)?
222            /var/run/cpglockd.pid
223            /var/run/corosync.pid
224            /var/run/rgmanager.pid
225            /var/run/cluster/rgmanager.sk
226
227       postfix_spool_type
228
229
230       postgrey_spool_t
231
232            /var/spool/postfix/postgrey(/.*)?
233
234       postgrey_var_lib_t
235
236            /var/lib/postgrey(/.*)?
237
238       postgrey_var_run_t
239
240            /var/run/postgrey(/.*)?
241            /var/run/postgrey.pid
242
243       root_t
244
245            /sysroot/ostree/deploy/.*-atomic.*/deploy(/.*)?
246            /
247            /initrd
248
249

FILE CONTEXTS

251       SELinux requires files to have an extended attribute to define the file
252       type.
253
254       You can see the context of a file using the -Z option to ls
255
256       Policy governs the access  confined  processes  have  to  these  files.
257       SELinux  postgrey policy is very flexible allowing users to setup their
258       postgrey processes in as secure a method as possible.
259
260       EQUIVALENCE DIRECTORIES
261
262
263       postgrey policy stores data with multiple different file context  types
264       under  the /var/run/postgrey directory.  If you would like to store the
265       data in a different directory you can use the semanage command to  cre‐
266       ate an equivalence mapping.  If you wanted to store this data under the
267       /srv dirctory you would execute the following command:
268
269       semanage fcontext -a -e /var/run/postgrey /srv/postgrey
270       restorecon -R -v /srv/postgrey
271
272       STANDARD FILE CONTEXT
273
274       SELinux defines the file context types for the postgrey, if you  wanted
275       to store files with these types in a diffent paths, you need to execute
276       the semanage command  to  sepecify  alternate  labeling  and  then  use
277       restorecon to put the labels on disk.
278
279       semanage   fcontext   -a  -t  postgrey_var_run_t  '/srv/mypostgrey_con‐
280       tent(/.*)?'
281       restorecon -R -v /srv/mypostgrey_content
282
283       Note: SELinux often uses regular expressions  to  specify  labels  that
284       match multiple files.
285
286       The following file types are defined for postgrey:
287
288
289
290       postgrey_etc_t
291
292       - Set files with the postgrey_etc_t type, if you want to store postgrey
293       files in the /etc directories.
294
295
296
297       postgrey_exec_t
298
299       - Set files with the postgrey_exec_t type, if you want to transition an
300       executable to the postgrey_t domain.
301
302
303
304       postgrey_initrc_exec_t
305
306       -  Set files with the postgrey_initrc_exec_t type, if you want to tran‐
307       sition an executable to the postgrey_initrc_t domain.
308
309
310
311       postgrey_spool_t
312
313       - Set files with the postgrey_spool_t type, if you want  to  store  the
314       postgrey files under the /var/spool directory.
315
316
317
318       postgrey_var_lib_t
319
320       -  Set files with the postgrey_var_lib_t type, if you want to store the
321       postgrey files under the /var/lib directory.
322
323
324
325       postgrey_var_run_t
326
327       - Set files with the postgrey_var_run_t type, if you want to store  the
328       postgrey files under the /run or /var/run directory.
329
330
331       Paths:
332            /var/run/postgrey(/.*)?, /var/run/postgrey.pid
333
334
335       Note:  File context can be temporarily modified with the chcon command.
336       If you want to permanently change the file context you need to use  the
337       semanage fcontext command.  This will modify the SELinux labeling data‐
338       base.  You will need to use restorecon to apply the labels.
339
340

COMMANDS

342       semanage fcontext can also be used to manipulate default  file  context
343       mappings.
344
345       semanage  permissive  can  also  be used to manipulate whether or not a
346       process type is permissive.
347
348       semanage module can also be used to enable/disable/install/remove  pol‐
349       icy modules.
350
351       semanage port can also be used to manipulate the port definitions
352
353       semanage boolean can also be used to manipulate the booleans
354
355
356       system-config-selinux is a GUI tool available to customize SELinux pol‐
357       icy settings.
358
359

AUTHOR

361       This manual page was auto-generated using sepolicy manpage .
362
363

SEE ALSO

365       selinux(8), postgrey(8), semanage(8), restorecon(8),  chcon(1),  sepol‐
366       icy(8) , setsebool(8)
367
368
369
370postgrey                           19-04-25                postgrey_selinux(8)
Impressum