NetworkManager_selinux(8)

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 deny all system processes and Linux users to use blue‐
64       tooth wireless technology, you must turn on the deny_bluetooth boolean.
65       Enabled by default.
66
67       setsebool -P deny_bluetooth 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  de‐
73       fault.
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 support ecryptfs home directories, you must turn on  the
87       use_ecryptfs_home_dirs boolean. Disabled by default.
88
89       setsebool -P use_ecryptfs_home_dirs 1
90
91
92
93       If  you  want  to  support  NFS  home directories, you must turn on the
94       use_nfs_home_dirs boolean. Disabled by default.
95
96       setsebool -P use_nfs_home_dirs 1
97
98
99
100       If you want to support SAMBA home directories, you  must  turn  on  the
101       use_samba_home_dirs boolean. Disabled by default.
102
103       setsebool -P use_samba_home_dirs 1
104
105
106
107       If you want to allow xguest users to configure Network Manager and con‐
108       nect to apache ports, you must turn on the xguest_connect_network bool‐
109       ean. Enabled by default.
110
111       setsebool -P xguest_connect_network 1
112
113
114

MANAGED FILES

116       The SELinux process type NetworkManager_t can manage files labeled with
117       the following file types.  The paths listed are the default  paths  for
118       these  file  types.  Note the processes UID still need to have DAC per‐
119       missions.
120
121       NetworkManager_etc_rw_t
122
123            /etc/NetworkManager/system-connections(/.*)?
124            /etc/NetworkManager/NetworkManager.conf
125
126       NetworkManager_tmp_t
127
128
129       NetworkManager_var_lib_t
130
131            /var/lib/wicd(/.*)?
132            /var/lib/NetworkManager(/.*)?
133            /etc/dhcp/wired-settings.conf
134            /etc/wicd/wired-settings.conf
135            /etc/dhcp/manager-settings.conf
136            /etc/wicd/manager-settings.conf
137            /etc/dhcp/wireless-settings.conf
138            /etc/wicd/wireless-settings.conf
139
140       NetworkManager_var_run_t
141
142            /var/run/teamd(/.*)?
143            /var/run/nm-xl2tpd.conf.*
144            /var/run/nm-dhclient.*
145            /var/run/NetworkManager(/.*)?
146            /var/run/wpa_supplicant(/.*)?
147            /var/run/wicd.pid
148            /var/run/NetworkManager.pid
149            /var/run/nm-dns-dnsmasq.conf
150            /var/run/wpa_supplicant-global
151
152       cluster_conf_t
153
154            /etc/cluster(/.*)?
155
156       cluster_var_lib_t
157
158            /var/lib/pcsd(/.*)?
159            /var/lib/cluster(/.*)?
160            /var/lib/openais(/.*)?
161            /var/lib/pengine(/.*)?
162            /var/lib/corosync(/.*)?
163            /usr/lib/heartbeat(/.*)?
164            /var/lib/heartbeat(/.*)?
165            /var/lib/pacemaker(/.*)?
166
167       cluster_var_run_t
168
169            /var/run/crm(/.*)?
170            /var/run/cman_.*
171            /var/run/rsctmp(/.*)?
172            /var/run/aisexec.*
173            /var/run/heartbeat(/.*)?
174            /var/run/pcsd-ruby.socket
175            /var/run/corosync-qnetd(/.*)?
176            /var/run/corosync-qdevice(/.*)?
177            /var/run/corosync.pid
178            /var/run/cpglockd.pid
179            /var/run/rgmanager.pid
180            /var/run/cluster/rgmanager.sk
181
182       dhcpc_state_t
183
184            /var/lib/dhcp3?/dhclient.*
185            /var/lib/dhcpcd(/.*)?
186            /var/lib/dhclient(/.*)?
187            /var/lib/wifiroamd(/.*)?
188
189       krb5_host_rcache_t
190
191            /var/tmp/krb5_0.rcache2
192            /var/cache/krb5rcache(/.*)?
193            /var/tmp/nfs_0
194            /var/tmp/DNS_25
195            /var/tmp/host_0
196            /var/tmp/imap_0
197            /var/tmp/HTTP_23
198            /var/tmp/HTTP_48
199            /var/tmp/ldap_55
200            /var/tmp/ldap_487
201            /var/tmp/ldapmap1_0
202
203       named_cache_t
204
205            /var/named/data(/.*)?
206            /var/lib/softhsm(/.*)?
207            /var/lib/unbound(/.*)?
208            /var/named/slaves(/.*)?
209            /var/named/dynamic(/.*)?
210            /var/named/chroot/var/tmp(/.*)?
211            /var/named/chroot/var/named/data(/.*)?
212            /var/named/chroot/var/named/slaves(/.*)?
213            /var/named/chroot/var/named/dynamic(/.*)?
214
215       pppd_var_run_t
216
217            /var/run/(i)?ppp.*pid[^/]*
218            /var/run/ppp(/.*)?
219            /var/run/pppd[0-9]*.tdb
220
221       root_t
222
223            /sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
224            /
225            /initrd
226
227       security_t
228
229            /selinux
230
231       sysfs_t
232
233            /sys(/.*)?
234
235       systemd_passwd_var_run_t
236
237            /var/run/systemd/ask-password(/.*)?
238            /var/run/systemd/ask-password-block(/.*)?
239
240

FILE CONTEXTS

242       SELinux requires files to have an extended attribute to define the file
243       type.
244
245       You can see the context of a file using the -Z option to ls
246
247       Policy  governs  the  access  confined  processes  have to these files.
248       SELinux NetworkManager policy is very flexible allowing users to  setup
249       their NetworkManager processes in as secure a method as possible.
250
251       EQUIVALENCE DIRECTORIES
252
253
254       NetworkManager  policy stores data with multiple different file context
255       types under the /var/run/NetworkManager directory.  If you  would  like
256       to  store  the  data  in a different directory you can use the semanage
257       command to create an equivalence mapping.  If you wanted to store  this
258       data under the /srv directory you would execute the following command:
259
260       semanage fcontext -a -e /var/run/NetworkManager /srv/NetworkManager
261       restorecon -R -v /srv/NetworkManager
262
263       NetworkManager  policy stores data with multiple different file context
264       types under the /var/run/wpa_supplicant directory.  If you  would  like
265       to  store  the  data  in a different directory you can use the semanage
266       command to create an equivalence mapping.  If you wanted to store  this
267       data under the /srv directory you would execute the following command:
268
269       semanage fcontext -a -e /var/run/wpa_supplicant /srv/wpa_supplicant
270       restorecon -R -v /srv/wpa_supplicant
271
272       STANDARD FILE CONTEXT
273
274       SELinux  defines  the file context types for the NetworkManager, if you
275       wanted to store files with these types in a diffent paths, you need  to
276       execute the semanage command to specify alternate labeling and then use
277       restorecon to put the labels on disk.
278
279       semanage fcontext -a  -t  NetworkManager_var_run_t  '/srv/myNetworkMan‐
280       ager_content(/.*)?'
281       restorecon -R -v /srv/myNetworkManager_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 NetworkManager:
287
288
289
290       NetworkManager_etc_rw_t
291
292       - Set files with the NetworkManager_etc_rw_t type, if you want to treat
293       the files as NetworkManager etc read/write content.
294
295
296       Paths:
297            /etc/NetworkManager/system-connections(/.*)?,     /etc/NetworkMan‐
298            ager/NetworkManager.conf
299
300
301       NetworkManager_etc_t
302
303       - Set files with the NetworkManager_etc_t type, if you  want  to  store
304       NetworkManager files in the /etc directories.
305
306
307
308       NetworkManager_exec_t
309
310       - Set files with the NetworkManager_exec_t type, if you want to transi‐
311       tion an executable to the NetworkManager_t domain.
312
313
314       Paths:
315            /usr/libexec/nm-dispatcher.*,   /usr/bin/teamd,    /usr/sbin/wicd,
316            /usr/bin/NetworkManager,  /usr/bin/wpa_supplicant,  /usr/sbin/Net‐
317            workManager,  /usr/sbin/wpa_supplicant,   /usr/sbin/nm-system-set‐
318            tings, /usr/sbin/NetworkManagerDispatcher
319
320
321       NetworkManager_initrc_exec_t
322
323       -  Set files with the NetworkManager_initrc_exec_t type, if you want to
324       transition an executable to the NetworkManager_initrc_t domain.
325
326
327       Paths:
328            /etc/NetworkManager/dispatcher.d(/.*)?,       /usr/lib/NetworkMan‐
329            ager/dispatcher.d(/.*)?, /etc/rc.d/init.d/wicd
330
331
332       NetworkManager_log_t
333
334       -  Set  files  with the NetworkManager_log_t type, if you want to treat
335       the data as NetworkManager log data, usually stored under the  /var/log
336       directory.
337
338
339       Paths:
340            /var/log/wicd.*, /var/log/wpa_supplicant.*
341
342
343       NetworkManager_tmp_t
344
345       -  Set  files  with the NetworkManager_tmp_t type, if you want to store
346       NetworkManager temporary files in the /tmp directories.
347
348
349
350       NetworkManager_unit_file_t
351
352       - Set files with the NetworkManager_unit_file_t type, if  you  want  to
353       treat the files as NetworkManager unit content.
354
355
356       Paths:
357            /usr/lib/systemd/system/NetworkManager.*,    /usr/lib/systemd/sys‐
358            tem/nm-cloud-setup.(service|timer)
359
360
361       NetworkManager_var_lib_t
362
363       - Set files with the NetworkManager_var_lib_t  type,  if  you  want  to
364       store the NetworkManager files under the /var/lib directory.
365
366
367       Paths:
368            /var/lib/wicd(/.*)?,                /var/lib/NetworkManager(/.*)?,
369            /etc/dhcp/wired-settings.conf,      /etc/wicd/wired-settings.conf,
370            /etc/dhcp/manager-settings.conf,  /etc/wicd/manager-settings.conf,
371            /etc/dhcp/wireless-settings.conf, /etc/wicd/wireless-settings.conf
372
373
374       NetworkManager_var_run_t
375
376       - Set files with the NetworkManager_var_run_t  type,  if  you  want  to
377       store the NetworkManager files under the /run or /var/run directory.
378
379
380       Paths:
381            /var/run/teamd(/.*)?,    /var/run/nm-xl2tpd.conf.*,   /var/run/nm-
382            dhclient.*,  /var/run/NetworkManager(/.*)?,   /var/run/wpa_suppli‐
383            cant(/.*)?,     /var/run/wicd.pid,    /var/run/NetworkManager.pid,
384            /var/run/nm-dns-dnsmasq.conf, /var/run/wpa_supplicant-global
385
386
387       Note: File context can be temporarily modified with the chcon  command.
388       If  you want to permanently change the file context you need to use the
389       semanage fcontext command.  This will modify the SELinux labeling data‐
390       base.  You will need to use restorecon to apply the labels.
391
392

COMMANDS

394       semanage  fcontext  can also be used to manipulate default file context
395       mappings.
396
397       semanage permissive can also be used to manipulate  whether  or  not  a
398       process type is permissive.
399
400       semanage  module can also be used to enable/disable/install/remove pol‐
401       icy modules.
402
403       semanage boolean can also be used to manipulate the booleans
404
405
406       system-config-selinux is a GUI tool available to customize SELinux pol‐
407       icy settings.
408
409

AUTHOR

411       This manual page was auto-generated using sepolicy manpage .
412
413