1NetworkManager_selinux(8)SELinux Policy NetworkManagerNetworkManager_selinux(8)
2
3
4

NAME

6       NetworkManager_selinux  -  Security  Enhanced Linux Policy for the Net‐
7       workManager processes
8

DESCRIPTION

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

ENTRYPOINTS

24       The  NetworkManager_t  SELinux  type can be entered via the NetworkMan‐
25       ager_exec_t file type.
26
27       The default entrypoint paths for the NetworkManager_t  domain  are  the
28       following:
29
30       /usr/libexec/nm-dispatcher.*,      /usr/bin/teamd,      /usr/sbin/wicd,
31       /usr/bin/NetworkManager, /usr/bin/wpa_supplicant, /usr/sbin/NetworkMan‐
32       ager,      /usr/sbin/wpa_supplicant,      /usr/sbin/nm-system-settings,
33       /usr/sbin/NetworkManagerDispatcher
34

PROCESS TYPES

36       SELinux defines process types (domains) for each process running on the
37       system
38
39       You can see the context of a process using the -Z option to ps
40
41       Policy  governs  the  access confined processes have to files.  SELinux
42       NetworkManager policy is very flexible allowing users  to  setup  their
43       NetworkManager processes in as secure a method as possible.
44
45       The following process types are defined for NetworkManager:
46
47       NetworkManager_t, NetworkManager_ssh_t
48
49       Note:  semanage  permissive -a NetworkManager_t can be used to make the
50       process type NetworkManager_t permissive. SELinux does not deny  access
51       to permissive process types, but the AVC (SELinux denials) messages are
52       still generated.
53
54

BOOLEANS

56       SELinux policy is customizable based on least  access  required.   Net‐
57       workManager  policy is extremely flexible and has several booleans that
58       allow you to manipulate the policy  and  run  NetworkManager  with  the
59       tightest access possible.
60
61
62
63       If you want to allow users to resolve user passwd entries directly from
64       ldap rather then using a sssd server, you  must  turn  on  the  authlo‐
65       gin_nsswitch_use_ldap boolean. Disabled by default.
66
67       setsebool -P authlogin_nsswitch_use_ldap 1
68
69
70
71       If  you  want  to deny any process from ptracing or debugging any other
72       processes, you  must  turn  on  the  deny_ptrace  boolean.  Enabled  by
73       default.
74
75       setsebool -P deny_ptrace 1
76
77
78
79       If you want to allow all domains to execute in fips_mode, you must turn
80       on the fips_mode boolean. Enabled by default.
81
82       setsebool -P fips_mode 1
83
84
85
86       If you want to allow confined applications to run  with  kerberos,  you
87       must turn on the kerberos_enabled boolean. Enabled by default.
88
89       setsebool -P kerberos_enabled 1
90
91
92
93       If  you  want  to  allow  system  to run with NIS, you must turn on the
94       nis_enabled boolean. Disabled by default.
95
96       setsebool -P nis_enabled 1
97
98
99
100       If you want to allow confined applications to use nscd  shared  memory,
101       you must turn on the nscd_use_shm boolean. Disabled by default.
102
103       setsebool -P nscd_use_shm 1
104
105
106
107       If  you want to support ecryptfs home directories, you must turn on the
108       use_ecryptfs_home_dirs boolean. Disabled by default.
109
110       setsebool -P use_ecryptfs_home_dirs 1
111
112
113
114       If you want to support NFS home  directories,  you  must  turn  on  the
115       use_nfs_home_dirs boolean. Disabled by default.
116
117       setsebool -P use_nfs_home_dirs 1
118
119
120
121       If  you  want  to  support SAMBA home directories, you must turn on the
122       use_samba_home_dirs boolean. Disabled by default.
123
124       setsebool -P use_samba_home_dirs 1
125
126
127
128       If you want to allow xguest users to configure Network Manager and con‐
129       nect to apache ports, you must turn on the xguest_connect_network bool‐
130       ean. Enabled by default.
131
132       setsebool -P xguest_connect_network 1
133
134
135

MANAGED FILES

137       The SELinux process type NetworkManager_t can manage files labeled with
138       the  following  file types.  The paths listed are the default paths for
139       these file types.  Note the processes UID still need to have  DAC  per‐
140       missions.
141
142       NetworkManager_etc_rw_t
143
144            /etc/NetworkManager/system-connections(/.*)?
145            /etc/NetworkManager/NetworkManager.conf
146
147       NetworkManager_tmp_t
148
149
150       NetworkManager_var_lib_t
151
152            /var/lib/wicd(/.*)?
153            /var/lib/NetworkManager(/.*)?
154            /etc/dhcp/wired-settings.conf
155            /etc/wicd/wired-settings.conf
156            /etc/dhcp/manager-settings.conf
157            /etc/wicd/manager-settings.conf
158            /etc/dhcp/wireless-settings.conf
159            /etc/wicd/wireless-settings.conf
160
161       NetworkManager_var_run_t
162
163            /var/run/teamd(/.*)?
164            /var/run/nm-xl2tpd.conf.*
165            /var/run/nm-dhclient.*
166            /var/run/NetworkManager(/.*)?
167            /var/run/wpa_supplicant(/.*)?
168            /var/run/wicd.pid
169            /var/run/NetworkManager.pid
170            /var/run/nm-dns-dnsmasq.conf
171            /var/run/wpa_supplicant-global
172
173       cluster_conf_t
174
175            /etc/cluster(/.*)?
176
177       cluster_var_lib_t
178
179            /var/lib/pcsd(/.*)?
180            /var/lib/cluster(/.*)?
181            /var/lib/openais(/.*)?
182            /var/lib/pengine(/.*)?
183            /var/lib/corosync(/.*)?
184            /usr/lib/heartbeat(/.*)?
185            /var/lib/heartbeat(/.*)?
186            /var/lib/pacemaker(/.*)?
187
188       cluster_var_run_t
189
190            /var/run/crm(/.*)?
191            /var/run/cman_.*
192            /var/run/rsctmp(/.*)?
193            /var/run/aisexec.*
194            /var/run/heartbeat(/.*)?
195            /var/run/corosync-qnetd(/.*)?
196            /var/run/corosync-qdevice(/.*)?
197            /var/run/corosync.pid
198            /var/run/cpglockd.pid
199            /var/run/rgmanager.pid
200            /var/run/cluster/rgmanager.sk
201
202       ecryptfs_t
203
204            /home/[^/]+/.Private(/.*)?
205            /home/[^/]+/.ecryptfs(/.*)?
206
207       hostname_etc_t
208
209            /etc/.*hostname.*
210            /etc/machine-info
211
212       named_cache_t
213
214            /var/named/data(/.*)?
215            /var/lib/softhsm(/.*)?
216            /var/lib/unbound(/.*)?
217            /var/named/slaves(/.*)?
218            /var/named/dynamic(/.*)?
219            /var/named/chroot/var/tmp(/.*)?
220            /var/named/chroot/var/named/data(/.*)?
221            /var/named/chroot/var/named/slaves(/.*)?
222            /var/named/chroot/var/named/dynamic(/.*)?
223
224       net_conf_t
225
226            /etc/hosts[^/]*
227            /etc/yp.conf.*
228            /etc/denyhosts.*
229            /etc/hosts.deny.*
230            /etc/resolv.conf.*
231            /etc/.resolv.conf.*
232            /etc/resolv-secure.conf.*
233            /var/run/cloud-init(/.*)?
234            /var/run/systemd/network(/.*)?
235            /etc/sysconfig/networking(/.*)?
236            /etc/sysconfig/network-scripts(/.*)?
237            /etc/sysconfig/network-scripts/.*resolv.conf
238            /var/run/NetworkManager/resolv.conf.*
239            /etc/ethers
240            /etc/ntp.conf
241            /var/run/systemd/resolve/resolv.conf
242            /var/run/systemd/resolve/stub-resolv.conf
243
244       pppd_var_run_t
245
246            /var/run/(i)?ppp.*pid[^/]*
247            /var/run/ppp(/.*)?
248            /var/run/pppd[0-9]*.tdb
249
250       root_t
251
252            /sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
253            /
254            /initrd
255
256       security_t
257
258            /selinux
259
260       ssh_home_t
261
262            /var/lib/[^/]+/.ssh(/.*)?
263            /root/.ssh(/.*)?
264            /var/lib/one/.ssh(/.*)?
265            /var/lib/pgsql/.ssh(/.*)?
266            /var/lib/openshift/[^/]+/.ssh(/.*)?
267            /var/lib/amanda/.ssh(/.*)?
268            /var/lib/stickshift/[^/]+/.ssh(/.*)?
269            /var/lib/gitolite/.ssh(/.*)?
270            /var/lib/nocpulse/.ssh(/.*)?
271            /var/lib/gitolite3/.ssh(/.*)?
272            /var/lib/openshift/gear/[^/]+/.ssh(/.*)?
273            /root/.shosts
274            /home/[^/]+/.ssh(/.*)?
275            /home/[^/]+/.ansible/cp/.*
276            /home/[^/]+/.shosts
277
278       sysfs_t
279
280            /sys(/.*)?
281
282       systemd_passwd_var_run_t
283
284            /var/run/systemd/ask-password(/.*)?
285            /var/run/systemd/ask-password-block(/.*)?
286
287

FILE CONTEXTS

289       SELinux requires files to have an extended attribute to define the file
290       type.
291
292       You can see the context of a file using the -Z option to ls
293
294       Policy governs the access  confined  processes  have  to  these  files.
295       SELinux  NetworkManager policy is very flexible allowing users to setup
296       their NetworkManager processes in as secure a method as possible.
297
298       EQUIVALENCE DIRECTORIES
299
300
301       NetworkManager policy stores data with multiple different file  context
302       types  under  the /var/run/NetworkManager directory.  If you would like
303       to store the data in a different directory you  can  use  the  semanage
304       command  to create an equivalence mapping.  If you wanted to store this
305       data under the /srv dirctory you would execute the following command:
306
307       semanage fcontext -a -e /var/run/NetworkManager /srv/NetworkManager
308       restorecon -R -v /srv/NetworkManager
309
310       NetworkManager policy stores data with multiple different file  context
311       types  under  the /var/run/wpa_supplicant directory.  If you would like
312       to store the data in a different directory you  can  use  the  semanage
313       command  to create an equivalence mapping.  If you wanted to store this
314       data under the /srv dirctory you would execute the following command:
315
316       semanage fcontext -a -e /var/run/wpa_supplicant /srv/wpa_supplicant
317       restorecon -R -v /srv/wpa_supplicant
318
319       STANDARD FILE CONTEXT
320
321       SELinux defines the file context types for the NetworkManager,  if  you
322       wanted  to store files with these types in a diffent paths, you need to
323       execute the semanage command to sepecify alternate  labeling  and  then
324       use restorecon to put the labels on disk.
325
326       semanage  fcontext  -a  -t NetworkManager_var_run_t '/srv/myNetworkMan‐
327       ager_content(/.*)?'
328       restorecon -R -v /srv/myNetworkManager_content
329
330       Note: SELinux often uses regular expressions  to  specify  labels  that
331       match multiple files.
332
333       The following file types are defined for NetworkManager:
334
335
336
337       NetworkManager_etc_rw_t
338
339       - Set files with the NetworkManager_etc_rw_t type, if you want to treat
340       the files as NetworkManager etc read/write content.
341
342
343       Paths:
344            /etc/NetworkManager/system-connections(/.*)?,     /etc/NetworkMan‐
345            ager/NetworkManager.conf
346
347
348       NetworkManager_etc_t
349
350       -  Set  files  with the NetworkManager_etc_t type, if you want to store
351       NetworkManager files in the /etc directories.
352
353
354
355       NetworkManager_exec_t
356
357       - Set files with the NetworkManager_exec_t type, if you want to transi‐
358       tion an executable to the NetworkManager_t domain.
359
360
361       Paths:
362            /usr/libexec/nm-dispatcher.*,    /usr/bin/teamd,   /usr/sbin/wicd,
363            /usr/bin/NetworkManager,  /usr/bin/wpa_supplicant,  /usr/sbin/Net‐
364            workManager,   /usr/sbin/wpa_supplicant,  /usr/sbin/nm-system-set‐
365            tings, /usr/sbin/NetworkManagerDispatcher
366
367
368       NetworkManager_initrc_exec_t
369
370       - Set files with the NetworkManager_initrc_exec_t type, if you want  to
371       transition an executable to the NetworkManager_initrc_t domain.
372
373
374       Paths:
375            /etc/NetworkManager/dispatcher.d(/.*)?, /etc/rc.d/init.d/wicd
376
377
378       NetworkManager_log_t
379
380       -  Set  files  with the NetworkManager_log_t type, if you want to treat
381       the data as NetworkManager log data, usually stored under the  /var/log
382       directory.
383
384
385       Paths:
386            /var/log/wicd.*, /var/log/wpa_supplicant.*
387
388
389       NetworkManager_tmp_t
390
391       -  Set  files  with the NetworkManager_tmp_t type, if you want to store
392       NetworkManager temporary files in the /tmp directories.
393
394
395
396       NetworkManager_unit_file_t
397
398       - Set files with the NetworkManager_unit_file_t type, if  you  want  to
399       treat the files as NetworkManager unit content.
400
401
402
403       NetworkManager_var_lib_t
404
405       -  Set  files  with  the  NetworkManager_var_lib_t type, if you want to
406       store the NetworkManager files under the /var/lib directory.
407
408
409       Paths:
410            /var/lib/wicd(/.*)?,                /var/lib/NetworkManager(/.*)?,
411            /etc/dhcp/wired-settings.conf,      /etc/wicd/wired-settings.conf,
412            /etc/dhcp/manager-settings.conf,  /etc/wicd/manager-settings.conf,
413            /etc/dhcp/wireless-settings.conf, /etc/wicd/wireless-settings.conf
414
415
416       NetworkManager_var_run_t
417
418       -  Set  files  with  the  NetworkManager_var_run_t type, if you want to
419       store the NetworkManager files under the /run or /var/run directory.
420
421
422       Paths:
423            /var/run/teamd(/.*)?,   /var/run/nm-xl2tpd.conf.*,    /var/run/nm-
424            dhclient.*,   /var/run/NetworkManager(/.*)?,  /var/run/wpa_suppli‐
425            cant(/.*)?,    /var/run/wicd.pid,     /var/run/NetworkManager.pid,
426            /var/run/nm-dns-dnsmasq.conf, /var/run/wpa_supplicant-global
427
428
429       Note:  File context can be temporarily modified with the chcon command.
430       If you want to permanently change the file context you need to use  the
431       semanage fcontext command.  This will modify the SELinux labeling data‐
432       base.  You will need to use restorecon to apply the labels.
433
434

COMMANDS

436       semanage fcontext can also be used to manipulate default  file  context
437       mappings.
438
439       semanage  permissive  can  also  be used to manipulate whether or not a
440       process type is permissive.
441
442       semanage module can also be used to enable/disable/install/remove  pol‐
443       icy modules.
444
445       semanage boolean can also be used to manipulate the booleans
446
447
448       system-config-selinux is a GUI tool available to customize SELinux pol‐
449       icy settings.
450
451

AUTHOR

453       This manual page was auto-generated using sepolicy manpage .
454
455

SEE ALSO

457       selinux(8), NetworkManager(8),  semanage(8),  restorecon(8),  chcon(1),
458       sepolicy(8),  setsebool(8),  NetworkManager_ssh_selinux(8), NetworkMan‐
459       ager_ssh_selinux(8)
460
461
462
463NetworkManager                     19-05-30          NetworkManager_selinux(8)
Impressum