1mdadm_selinux(8)             SELinux Policy mdadm             mdadm_selinux(8)
2
3
4

NAME

6       mdadm_selinux - Security Enhanced Linux Policy for the mdadm processes
7

DESCRIPTION

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

ENTRYPOINTS

23       The  mdadm_t  SELinux  type  can  be   entered   via   the   file_type,
24       mdadm_exec_t,  unlabeled_t,  proc_type, filesystem_type, mtrr_device_t,
25       sysctl_type file types.
26
27       The default entrypoint paths for the mdadm_t domain are the following:
28
29       all files on the system, /sbin/mdadm,  /sbin/mdmpd,  /usr/sbin/iprdump,
30       /usr/sbin/iprinit, /usr/sbin/iprupdate, /dev/cpu/mtrr
31

PROCESS TYPES

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

BOOLEANS

53       SELinux  policy  is customizable based on least access required.  mdadm
54       policy is extremely flexible and has several booleans that allow you to
55       manipulate the policy and run mdadm with the tightest access possible.
56
57
58
59       If you want to allow all daemons to write corefiles to /, you must turn
60       on the allow_daemons_dump_core boolean. Disabled by default.
61
62       setsebool -P allow_daemons_dump_core 1
63
64
65
66       If you want to allow all daemons to use tcp wrappers, you must turn  on
67       the allow_daemons_use_tcp_wrapper boolean. Disabled by default.
68
69       setsebool -P allow_daemons_use_tcp_wrapper 1
70
71
72
73       If  you  want to allow all daemons the ability to read/write terminals,
74       you  must  turn  on  the  allow_daemons_use_tty  boolean.  Disabled  by
75       default.
76
77       setsebool -P allow_daemons_use_tty 1
78
79
80
81       If you want to allow all domains to use other domains file descriptors,
82       you must turn on the allow_domain_fd_use boolean. Enabled by default.
83
84       setsebool -P allow_domain_fd_use 1
85
86
87
88       If you want to allow unconfined executables to make their  heap  memory
89       executable.   Doing  this  is  a  really bad idea. Probably indicates a
90       badly coded executable, but could indicate an attack.  This  executable
91       should  be  reported  in  bugzilla, you must turn on the allow_execheap
92       boolean. Disabled by default.
93
94       setsebool -P allow_execheap 1
95
96
97
98       If you want to allow unconfined executables to map a memory  region  as
99       both  executable  and  writable,  this  is dangerous and the executable
100       should be reported in bugzilla), you must  turn  on  the  allow_execmem
101       boolean. Enabled by default.
102
103       setsebool -P allow_execmem 1
104
105
106
107       If  you  want  to  allow  all  unconfined  executables to use libraries
108       requiring text relocation that are not  labeled  textrel_shlib_t),  you
109       must turn on the allow_execmod boolean. Enabled by default.
110
111       setsebool -P allow_execmod 1
112
113
114
115       If  you  want  to allow unconfined executables to make their stack exe‐
116       cutable.  This should never, ever be necessary.  Probably  indicates  a
117       badly  coded  executable, but could indicate an attack. This executable
118       should be reported in bugzilla), you must turn on  the  allow_execstack
119       boolean. Enabled by default.
120
121       setsebool -P allow_execstack 1
122
123
124
125       If  you want to allow sysadm to debug or ptrace all processes, you must
126       turn on the allow_ptrace boolean. Disabled by default.
127
128       setsebool -P allow_ptrace 1
129
130
131
132       If you want to enable cluster mode for daemons, you must  turn  on  the
133       daemons_enable_cluster_mode boolean. Disabled by default.
134
135       setsebool -P daemons_enable_cluster_mode 1
136
137
138
139       If  you  want to allow all domains to have the kernel load modules, you
140       must  turn  on  the  domain_kernel_load_modules  boolean.  Disabled  by
141       default.
142
143       setsebool -P domain_kernel_load_modules 1
144
145
146
147       If you want to allow all domains to execute in fips_mode, you must turn
148       on the fips_mode boolean. Enabled by default.
149
150       setsebool -P fips_mode 1
151
152
153
154       If you want to enable reading of urandom for all domains, you must turn
155       on the global_ssp boolean. Disabled by default.
156
157       setsebool -P global_ssp 1
158
159
160
161       If you want to enable support for upstart as the init program, you must
162       turn on the init_upstart boolean. Enabled by default.
163
164       setsebool -P init_upstart 1
165
166
167
168       If you want to allow certain domains to map low memory in  the  kernel,
169       you must turn on the mmap_low_allowed boolean. Disabled by default.
170
171       setsebool -P mmap_low_allowed 1
172
173
174
175       If  you want to boolean to determine whether the system permits loading
176       policy, setting enforcing mode, and changing boolean values.  Set  this
177       to  true  and  you  have to reboot to set it back, you must turn on the
178       secure_mode_policyload boolean. Disabled by default.
179
180       setsebool -P secure_mode_policyload 1
181
182
183
184       If you want to support X userspace object manager, you must turn on the
185       xserver_object_manager boolean. Disabled by default.
186
187       setsebool -P xserver_object_manager 1
188
189
190

MANAGED FILES

192       The SELinux process type mdadm_t can manage files labeled with the fol‐
193       lowing file types.  The paths listed are the default  paths  for  these
194       file types.  Note the processes UID still need to have DAC permissions.
195
196       file_type
197
198            all files on the system
199
200

FILE CONTEXTS

202       SELinux requires files to have an extended attribute to define the file
203       type.
204
205       You can see the context of a file using the -Z option to ls
206
207       Policy governs the access  confined  processes  have  to  these  files.
208       SELinux  mdadm  policy  is  very flexible allowing users to setup their
209       mdadm processes in as secure a method as possible.
210
211       STANDARD FILE CONTEXT
212
213       SELinux defines the file context types for the mdadm, if you wanted  to
214       store  files  with  these types in a diffent paths, you need to execute
215       the semanage command  to  sepecify  alternate  labeling  and  then  use
216       restorecon to put the labels on disk.
217
218       semanage fcontext -a -t mdadm_var_run_t '/srv/mymdadm_content(/.*)?'
219       restorecon -R -v /srv/mymdadm_content
220
221       Note:  SELinux  often  uses  regular expressions to specify labels that
222       match multiple files.
223
224       The following file types are defined for mdadm:
225
226
227
228       mdadm_exec_t
229
230       - Set files with the mdadm_exec_t type, if you want  to  transition  an
231       executable to the mdadm_t domain.
232
233
234       Paths:
235            /sbin/mdadm,  /sbin/mdmpd,  /usr/sbin/iprdump,  /usr/sbin/iprinit,
236            /usr/sbin/iprupdate
237
238
239       mdadm_map_t
240
241       - Set files with the mdadm_map_t type, if you want to treat  the  files
242       as mdadm map data.
243
244
245
246       mdadm_var_run_t
247
248       -  Set  files  with  the mdadm_var_run_t type, if you want to store the
249       mdadm files under the /run or /var/run directory.
250
251
252
253       Note: File context can be temporarily modified with the chcon  command.
254       If  you want to permanently change the file context you need to use the
255       semanage fcontext command.  This will modify the SELinux labeling data‐
256       base.  You will need to use restorecon to apply the labels.
257
258

COMMANDS

260       semanage  fcontext  can also be used to manipulate default file context
261       mappings.
262
263       semanage permissive can also be used to manipulate  whether  or  not  a
264       process type is permissive.
265
266       semanage  module can also be used to enable/disable/install/remove pol‐
267       icy modules.
268
269       semanage boolean can also be used to manipulate the booleans
270
271
272       system-config-selinux is a GUI tool available to customize SELinux pol‐
273       icy settings.
274
275

AUTHOR

277       This manual page was auto-generated using sepolicy manpage .
278
279

SEE ALSO

281       selinux(8),  mdadm(8),  semanage(8),  restorecon(8),  chcon(1) , setse‐
282       bool(8)
283
284
285
286mdadm                              15-06-03                   mdadm_selinux(8)
Impressum