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
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 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. Enabled 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_var_lib_t
127
128            /var/lib/wicd(/.*)?
129            /var/lib/NetworkManager(/.*)?
130            /etc/dhcp/wired-settings.conf
131            /etc/wicd/wired-settings.conf
132            /etc/dhcp/manager-settings.conf
133            /etc/wicd/manager-settings.conf
134            /etc/dhcp/wireless-settings.conf
135            /etc/wicd/wireless-settings.conf
136
137       NetworkManager_var_run_t
138
139            /var/run/teamd(/.*)?
140            /var/run/nm-xl2tpd.conf.*
141            /var/run/nm-dhclient.*
142            /var/run/NetworkManager(/.*)?
143            /var/run/wpa_supplicant(/.*)?
144            /var/run/wicd.pid
145            /var/run/NetworkManager.pid
146            /var/run/nm-dns-dnsmasq.conf
147            /var/run/wpa_supplicant-global
148
149       cluster_conf_t
150
151            /etc/cluster(/.*)?
152
153       cluster_var_lib_t
154
155            /var/lib/pcsd(/.*)?
156            /var/lib/cluster(/.*)?
157            /var/lib/openais(/.*)?
158            /var/lib/pengine(/.*)?
159            /var/lib/corosync(/.*)?
160            /usr/lib/heartbeat(/.*)?
161            /var/lib/heartbeat(/.*)?
162            /var/lib/pacemaker(/.*)?
163
164       cluster_var_run_t
165
166            /var/run/crm(/.*)?
167            /var/run/cman_.*
168            /var/run/rsctmp(/.*)?
169            /var/run/aisexec.*
170            /var/run/heartbeat(/.*)?
171            /var/run/corosync-qnetd(/.*)?
172            /var/run/corosync-qdevice(/.*)?
173            /var/run/corosync.pid
174            /var/run/cpglockd.pid
175            /var/run/rgmanager.pid
176            /var/run/cluster/rgmanager.sk
177
178       dhcpc_state_t
179
180            /var/lib/dhcp3?/dhclient.*
181            /var/lib/dhcpcd(/.*)?
182            /var/lib/dhclient(/.*)?
183            /var/lib/wifiroamd(/.*)?
184
185       named_cache_t
186
187            /var/named/data(/.*)?
188            /var/lib/softhsm(/.*)?
189            /var/lib/unbound(/.*)?
190            /var/named/slaves(/.*)?
191            /var/named/dynamic(/.*)?
192            /var/named/chroot/var/tmp(/.*)?
193            /var/named/chroot/var/named/data(/.*)?
194            /var/named/chroot/var/named/slaves(/.*)?
195            /var/named/chroot/var/named/dynamic(/.*)?
196
197       pppd_var_run_t
198
199            /var/run/(i)?ppp.*pid[^/]*
200            /var/run/ppp(/.*)?
201            /var/run/pppd[0-9]*.tdb
202
203       root_t
204
205            /sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
206            /
207            /initrd
208
209       security_t
210
211            /selinux
212
213       sysfs_t
214
215            /sys(/.*)?
216
217       systemd_passwd_var_run_t
218
219            /var/run/systemd/ask-password(/.*)?
220            /var/run/systemd/ask-password-block(/.*)?
221
222

FILE CONTEXTS

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

COMMANDS

376       semanage  fcontext  can also be used to manipulate default file context
377       mappings.
378
379       semanage permissive can also be used to manipulate  whether  or  not  a
380       process type is permissive.
381
382       semanage  module can also be used to enable/disable/install/remove pol‐
383       icy modules.
384
385       semanage boolean can also be used to manipulate the booleans
386
387
388       system-config-selinux is a GUI tool available to customize SELinux pol‐
389       icy settings.
390
391

AUTHOR

393       This manual page was auto-generated using sepolicy manpage .
394
395