cloud_init_selinux(8)

1cloud_init_selinux(8)      SELinux Policy cloud_init     cloud_init_selinux(8)
2
3
4

NAME

6       cloud_init_selinux  - Security Enhanced Linux Policy for the cloud_init
7       processes
8

DESCRIPTION

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

ENTRYPOINTS

24       The  cloud_init_t SELinux type can be entered via the cloud_init_exec_t
25       file type.
26
27       The default entrypoint paths for the cloud_init_t domain are  the  fol‐
28       lowing:
29
30       /usr/lib/systemd/system-generators/cloud-init.*,   /usr/bin/cloud-init,
31       /usr/libexec/min-cloud-agent, /usr/libexec/min-metadata-service
32

PROCESS TYPES

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

BOOLEANS

54       SELinux  policy  is  customizable  based  on  least  access   required.
55       cloud_init  policy  is extremely flexible and has several booleans that
56       allow you to manipulate the policy and run cloud_init with the tightest
57       access possible.
58
59
60
61       If you want to allow users to resolve user passwd entries directly from
62       ldap rather then using a sssd server, you  must  turn  on  the  authlo‐
63       gin_nsswitch_use_ldap boolean. Disabled by default.
64
65       setsebool -P authlogin_nsswitch_use_ldap 1
66
67
68
69       If you want to deny user domains applications to map a memory region as
70       both executable and writable, this  is  dangerous  and  the  executable
71       should be reported in bugzilla, you must turn on the deny_execmem bool‐
72       ean. Enabled by default.
73
74       setsebool -P deny_execmem 1
75
76
77
78       If you want to allow all domains to execute in fips_mode, you must turn
79       on the fips_mode boolean. Enabled by default.
80
81       setsebool -P fips_mode 1
82
83
84
85       If  you  want  to allow confined applications to run with kerberos, you
86       must turn on the kerberos_enabled boolean. Enabled by default.
87
88       setsebool -P kerberos_enabled 1
89
90
91
92       If you want to control the ability to mmap a low area  of  the  address
93       space,  as  configured  by /proc/sys/vm/mmap_min_addr, you must turn on
94       the mmap_low_allowed boolean. Disabled by default.
95
96       setsebool -P mmap_low_allowed 1
97
98
99
100       If you want to allow system to run with  NIS,  you  must  turn  on  the
101       nis_enabled boolean. Disabled by default.
102
103       setsebool -P nis_enabled 1
104
105
106
107       If  you  want to allow confined applications to use nscd shared memory,
108       you must turn on the nscd_use_shm boolean. Enabled by default.
109
110       setsebool -P nscd_use_shm 1
111
112
113
114       If you want to disable kernel module loading,  you  must  turn  on  the
115       secure_mode_insmod boolean. Enabled by default.
116
117       setsebool -P secure_mode_insmod 1
118
119
120
121       If  you  want to allow unconfined executables to make their heap memory
122       executable.  Doing this is a really  bad  idea.  Probably  indicates  a
123       badly  coded  executable, but could indicate an attack. This executable
124       should  be  reported  in  bugzilla,  you  must  turn  on   the   selin‐
125       uxuser_execheap boolean. Disabled by default.
126
127       setsebool -P selinuxuser_execheap 1
128
129
130
131       If  you  want  to allow unconfined executables to make their stack exe‐
132       cutable.  This should never, ever be necessary.  Probably  indicates  a
133       badly  coded  executable, but could indicate an attack. This executable
134       should be reported in bugzilla, you must turn on the  selinuxuser_exec‐
135       stack boolean. Enabled by default.
136
137       setsebool -P selinuxuser_execstack 1
138
139
140

MANAGED FILES

142       The SELinux process type cloud_init_t can manage files labeled with the
143       following file types.  The paths listed are the default paths for these
144       file types.  Note the processes UID still need to have DAC permissions.
145
146       file_type
147
148            all files on the system
149
150

FILE CONTEXTS

152       SELinux requires files to have an extended attribute to define the file
153       type.
154
155       You can see the context of a file using the -Z option to ls
156
157       Policy governs the access  confined  processes  have  to  these  files.
158       SELinux  cloud_init  policy  is  very  flexible allowing users to setup
159       their cloud_init processes in as secure a method as possible.
160
161       STANDARD FILE CONTEXT
162
163       SELinux defines the file context  types  for  the  cloud_init,  if  you
164       wanted  to store files with these types in a diffent paths, you need to
165       execute the semanage command to sepecify alternate  labeling  and  then
166       use restorecon to put the labels on disk.
167
168       semanage  fcontext -a -t cloud_init_unit_file_t '/srv/mycloud_init_con‐
169       tent(/.*)?'
170       restorecon -R -v /srv/mycloud_init_content
171
172       Note: SELinux often uses regular expressions  to  specify  labels  that
173       match multiple files.
174
175       The following file types are defined for cloud_init:
176
177
178
179       cloud_init_exec_t
180
181       -  Set files with the cloud_init_exec_t type, if you want to transition
182       an executable to the cloud_init_t domain.
183
184
185       Paths:
186            /usr/lib/systemd/system-generators/cloud-init.*,   /usr/bin/cloud-
187            init, /usr/libexec/min-cloud-agent, /usr/libexec/min-metadata-ser‐
188            vice
189
190
191       cloud_init_tmp_t
192
193       - Set files with the cloud_init_tmp_t type, if you want to store  cloud
194       init temporary files in the /tmp directories.
195
196
197
198       cloud_init_unit_file_t
199
200       -  Set files with the cloud_init_unit_file_t type, if you want to treat
201       the files as cloud init unit content.
202
203
204       Paths:
205            /usr/lib/systemd/system/cloud-init.*,        /usr/lib/systemd/sys‐
206            tem/cloud-config.*
207
208
209       Note:  File context can be temporarily modified with the chcon command.
210       If you want to permanently change the file context you need to use  the
211       semanage fcontext command.  This will modify the SELinux labeling data‐
212       base.  You will need to use restorecon to apply the labels.
213
214

COMMANDS

216       semanage fcontext can also be used to manipulate default  file  context
217       mappings.
218
219       semanage  permissive  can  also  be used to manipulate whether or not a
220       process type is permissive.
221
222       semanage module can also be used to enable/disable/install/remove  pol‐
223       icy modules.
224
225       semanage boolean can also be used to manipulate the booleans
226
227
228       system-config-selinux is a GUI tool available to customize SELinux pol‐
229       icy settings.
230
231

AUTHOR

233       This manual page was auto-generated using sepolicy manpage .
234
235