1NetworkManager_diSsEpLaitncuhxerP_oclliocuyd_NseetlwionrNukexMt(aw8no)argkeMra_ndaigsepra_tdcihsepra_tcclhoeurd_cloud_selinux(8)
2
3
4
6 NetworkManager_dispatcher_cloud_selinux - Security Enhanced Linux Pol‐
7 icy for the NetworkManager_dispatcher_cloud processes
8
10 Security-Enhanced Linux secures the NetworkManager_dispatcher_cloud
11 processes via flexible mandatory access control.
12
13 The NetworkManager_dispatcher_cloud processes execute with the Network‐
14 Manager_dispatcher_cloud_t SELinux type. You can check if you have
15 these processes running by executing the ps command with the -Z quali‐
16 fier.
17
18 For example:
19
20 ps -eZ | grep NetworkManager_dispatcher_cloud_t
21
22
23
25 The NetworkManager_dispatcher_cloud_t SELinux type can be entered via
26 the NetworkManager_dispatcher_cloud_script_t file type.
27
28 The default entrypoint paths for the NetworkManager_dispatcher_cloud_t
29 domain are the following:
30
31 /etc/NetworkManager/dispatcher.d/hook-network-manager, /etc/NetworkMan‐
32 ager/dispatcher.d/cloud-init-azure-hook, /usr/lib/NetworkManager/dis‐
33 patcher.d/90-nm-cloud-setup.sh, /usr/lib/NetworkManager/dis‐
34 patcher.d/no-wait.d/90-nm-cloud-setup.sh
35
37 SELinux defines process types (domains) for each process running on the
38 system
39
40 You can see the context of a process using the -Z option to ps
41
42 Policy governs the access confined processes have to files. SELinux
43 NetworkManager_dispatcher_cloud policy is very flexible allowing users
44 to setup their NetworkManager_dispatcher_cloud processes in as secure a
45 method as possible.
46
47 The following process types are defined for NetworkManager_dis‐
48 patcher_cloud:
49
50 NetworkManager_dispatcher_cloud_t
51
52 Note: semanage permissive -a NetworkManager_dispatcher_cloud_t can be
53 used to make the process type NetworkManager_dispatcher_cloud_t permis‐
54 sive. SELinux does not deny access to permissive process types, but the
55 AVC (SELinux denials) messages are still generated.
56
57
59 SELinux policy is customizable based on least access required. Net‐
60 workManager_dispatcher_cloud policy is extremely flexible and has sev‐
61 eral booleans that allow you to manipulate the policy and run Network‐
62 Manager_dispatcher_cloud with the tightest access possible.
63
64
65
66 If you want to allow all domains to execute in fips_mode, you must turn
67 on the fips_mode boolean. Enabled by default.
68
69 setsebool -P fips_mode 1
70
71
72
74 The SELinux process type NetworkManager_dispatcher_cloud_t can manage
75 files labeled with the following file types. The paths listed are the
76 default paths for these file types. Note the processes UID still need
77 to have DAC permissions.
78
79 systemd_passwd_var_run_t
80
81 /var/run/systemd/ask-password(/.*)?
82 /var/run/systemd/ask-password-block(/.*)?
83
84
86 SELinux requires files to have an extended attribute to define the file
87 type.
88
89 You can see the context of a file using the -Z option to ls
90
91 Policy governs the access confined processes have to these files.
92 SELinux NetworkManager_dispatcher_cloud policy is very flexible allow‐
93 ing users to setup their NetworkManager_dispatcher_cloud processes in
94 as secure a method as possible.
95
96 STANDARD FILE CONTEXT
97
98 SELinux defines the file context types for the NetworkManager_dis‐
99 patcher_cloud, if you wanted to store files with these types in a dif‐
100 ferent paths, you need to execute the semanage command to specify al‐
101 ternate labeling and then use restorecon to put the labels on disk.
102
103 semanage fcontext -a -t NetworkManager_dispatcher_cloud_script_t
104 '/srv/NetworkManager_dispatcher_cloud/content(/.*)?'
105 restorecon -R -v /srv/myNetworkManager_dispatcher_cloud_content
106
107 Note: SELinux often uses regular expressions to specify labels that
108 match multiple files.
109
110 The following file types are defined for NetworkManager_dis‐
111 patcher_cloud:
112
113
114
115 NetworkManager_dispatcher_cloud_script_t
116
117 - Set files with the NetworkManager_dispatcher_cloud_script_t type, if
118 you want to treat the files as NetworkManager dispatcher cloud script
119 data.
120
121
122 Paths:
123 /etc/NetworkManager/dispatcher.d/hook-network-manager, /etc/Net‐
124 workManager/dispatcher.d/cloud-init-azure-hook, /usr/lib/Network‐
125 Manager/dispatcher.d/90-nm-cloud-setup.sh, /usr/lib/NetworkMan‐
126 ager/dispatcher.d/no-wait.d/90-nm-cloud-setup.sh
127
128
129 Note: File context can be temporarily modified with the chcon command.
130 If you want to permanently change the file context you need to use the
131 semanage fcontext command. This will modify the SELinux labeling data‐
132 base. You will need to use restorecon to apply the labels.
133
134
136 semanage fcontext can also be used to manipulate default file context
137 mappings.
138
139 semanage permissive can also be used to manipulate whether or not a
140 process type is permissive.
141
142 semanage module can also be used to enable/disable/install/remove pol‐
143 icy modules.
144
145 semanage boolean can also be used to manipulate the booleans
146
147
148 system-config-selinux is a GUI tool available to customize SELinux pol‐
149 icy settings.
150
151
153 This manual page was auto-generated using sepolicy manpage .
154
155
157 selinux(8), NetworkManager_dispatcher_cloud(8), semanage(8), restore‐
158 con(8), chcon(1), sepolicy(8), setsebool(8)
159
160
161
162NetworkManager_dispatcher_cloud 23N-e1t0w-o2r0kManager_dispatcher_cloud_selinux(8)