systemd_resolved_selinux(8)

1systemd_resolved_selinux(S8E)Linux Policy systemd_resolsvyesdtemd_resolved_selinux(8)
2
3
4

NAME

6       systemd_resolved_selinux  - Security Enhanced Linux Policy for the sys‐
7       temd_resolved processes
8

DESCRIPTION

10       Security-Enhanced Linux  secures  the  systemd_resolved  processes  via
11       flexible mandatory access control.
12
13       The  systemd_resolved  processes  execute  with  the systemd_resolved_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 systemd_resolved_t
20
21
22

ENTRYPOINTS

24       The  systemd_resolved_t  SELinux  type  can  be  entered  via  the sys‐
25       temd_resolved_exec_t file type.
26
27       The default entrypoint paths for the systemd_resolved_t domain are  the
28       following:
29
30       /usr/lib/systemd/systemd-resolve(d|-host)
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       systemd_resolved  policy is very flexible allowing users to setup their
40       systemd_resolved processes in as secure a method as possible.
41
42       The following process types are defined for systemd_resolved:
43
44       systemd_resolved_t
45
46       Note: semanage permissive -a systemd_resolved_t can be used to make the
47       process  type  systemd_resolved_t  permissive.  SELinux  does  not deny
48       access to permissive process types, but the AVC (SELinux denials)  mes‐
49       sages are still generated.
50
51

BOOLEANS

53       SELinux  policy  is  customizable based on least access required.  sys‐
54       temd_resolved policy is extremely flexible  and  has  several  booleans
55       that  allow  you to manipulate the policy and run systemd_resolved 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

MANAGED FILES

171       The SELinux process type systemd_resolved_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       net_conf_t
206
207            /etc/hosts[^/]*
208            /etc/yp.conf.*
209            /etc/denyhosts.*
210            /etc/hosts.deny.*
211            /etc/resolv.conf.*
212            /etc/.resolv.conf.*
213            /etc/resolv-secure.conf.*
214            /var/run/systemd/network(/.*)?
215            /etc/sysconfig/networking(/.*)?
216            /etc/sysconfig/network-scripts(/.*)?
217            /etc/sysconfig/network-scripts/.*resolv.conf
218            /var/run/NetworkManager/resolv.conf.*
219            /etc/ethers
220            /etc/ntp.conf
221            /var/run/systemd/resolve/resolv.conf
222
223       root_t
224
225            /sysroot/ostree/deploy/.*-atomic.*/deploy(/.*)?
226            /
227            /initrd
228
229       systemd_resolved_var_run_t
230
231            /var/run/systemd/resolve(/.*)?
232
233

FILE CONTEXTS

235       SELinux requires files to have an extended attribute to define the file
236       type.
237
238       You can see the context of a file using the -Z option to ls
239
240       Policy governs the access  confined  processes  have  to  these  files.
241       SELinux systemd_resolved policy is very flexible allowing users to set‐
242       up their systemd_resolved processes in as secure a method as possible.
243
244       STANDARD FILE CONTEXT
245
246       SELinux defines the file context types for the systemd_resolved, if you
247       wanted  to store files with these types in a diffent paths, you need to
248       execute the semanage command to sepecify alternate  labeling  and  then
249       use restorecon to put the labels on disk.
250
251       semanage   fcontext   -a   -t  systemd_resolved_var_run_t  '/srv/mysys‐
252       temd_resolved_content(/.*)?'
253       restorecon -R -v /srv/mysystemd_resolved_content
254
255       Note: SELinux often uses regular expressions  to  specify  labels  that
256       match multiple files.
257
258       The following file types are defined for systemd_resolved:
259
260
261
262       systemd_resolved_exec_t
263
264       - Set files with the systemd_resolved_exec_t type, if you want to tran‐
265       sition an executable to the systemd_resolved_t domain.
266
267
268
269       systemd_resolved_unit_file_t
270
271       - Set files with the systemd_resolved_unit_file_t type, if you want  to
272       treat the files as systemd resolved unit content.
273
274
275
276       systemd_resolved_var_run_t
277
278       -  Set  files  with the systemd_resolved_var_run_t type, if you want to
279       store the systemd resolved files under the /run or /var/run directory.
280
281
282
283       Note: File context can be temporarily modified with the chcon  command.
284       If  you want to permanently change the file context you need to use the
285       semanage fcontext command.  This will modify the SELinux labeling data‐
286       base.  You will need to use restorecon to apply the labels.
287
288

COMMANDS

290       semanage  fcontext  can also be used to manipulate default file context
291       mappings.
292
293       semanage permissive can also be used to manipulate  whether  or  not  a
294       process type is permissive.
295
296       semanage  module can also be used to enable/disable/install/remove pol‐
297       icy modules.
298
299       semanage boolean can also be used to manipulate the booleans
300
301
302       system-config-selinux is a GUI tool available to customize SELinux pol‐
303       icy settings.
304
305

AUTHOR

307       This manual page was auto-generated using sepolicy manpage .
308
309