svnserve_selinux(8)

1svnserve_selinux(8)         SELinux Policy svnserve        svnserve_selinux(8)
2
3
4

NAME

6       svnserve_selinux - Security Enhanced Linux Policy for the svnserve pro‐
7       cesses
8

DESCRIPTION

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

ENTRYPOINTS

24       The  svnserve_t  SELinux  type  can be entered via the file_type, unla‐
25       beled_t, proc_type,  filesystem_type,  svnserve_exec_t,  mtrr_device_t,
26       sysctl_type file types.
27
28       The  default entrypoint paths for the svnserve_t domain are the follow‐
29       ing:
30
31       all files on the system, /usr/bin/svnserve, /dev/cpu/mtrr
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       svnserve policy is very flexible allowing users to setup their svnserve
41       processes in as secure a method as possible.
42
43       The following process types are defined for svnserve:
44
45       svnserve_t
46
47       Note: semanage permissive -a svnserve_t can be used to make the process
48       type svnserve_t permissive. SELinux does not deny access to  permissive
49       process  types, but the AVC (SELinux denials) messages are still gener‐
50       ated.
51
52

BOOLEANS

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

MANAGED FILES

194       The  SELinux  process type svnserve_t can manage files labeled with the
195       following file types.  The paths listed are the default paths for these
196       file types.  Note the processes UID still need to have DAC permissions.
197
198       file_type
199
200            all files on the system
201
202

FILE CONTEXTS

204       SELinux requires files to have an extended attribute to define the file
205       type.
206
207       You can see the context of a file using the -Z option to ls
208
209       Policy governs the access  confined  processes  have  to  these  files.
210       SELinux  svnserve policy is very flexible allowing users to setup their
211       svnserve processes in as secure a method as possible.
212
213       EQUIVALENCE DIRECTORIES
214
215
216       svnserve policy stores data with multiple different file context  types
217       under  the /var/run/svnserve directory.  If you would like to store the
218       data in a different directory you can use the semanage command to  cre‐
219       ate an equivalence mapping.  If you wanted to store this data under the
220       /srv dirctory you would execute the following command:
221
222       semanage fcontext -a -e /var/run/svnserve /srv/svnserve
223       restorecon -R -v /srv/svnserve
224
225       STANDARD FILE CONTEXT
226
227       SELinux defines the file context types for the svnserve, if you  wanted
228       to store files with these types in a diffent paths, you need to execute
229       the semanage command  to  sepecify  alternate  labeling  and  then  use
230       restorecon to put the labels on disk.
231
232       semanage   fcontext   -a  -t  svnserve_var_run_t  '/srv/mysvnserve_con‐
233       tent(/.*)?'
234       restorecon -R -v /srv/mysvnserve_content
235
236       Note: SELinux often uses regular expressions  to  specify  labels  that
237       match multiple files.
238
239       The following file types are defined for svnserve:
240
241
242
243       svnserve_content_t
244
245       -  Set files with the svnserve_content_t type, if you want to treat the
246       files as svnserve content.
247
248
249       Paths:
250            /var/subversion/repo(/.*)?, /var/lib/subversion/repo(/.*)?
251
252
253       svnserve_exec_t
254
255       - Set files with the svnserve_exec_t type, if you want to transition an
256       executable to the svnserve_t domain.
257
258
259
260       svnserve_initrc_exec_t
261
262       -  Set files with the svnserve_initrc_exec_t type, if you want to tran‐
263       sition an executable to the svnserve_initrc_t domain.
264
265
266
267       svnserve_var_run_t
268
269       - Set files with the svnserve_var_run_t type, if you want to store  the
270       svnserve files under the /run or /var/run directory.
271
272
273       Paths:
274            /var/run/svnserve.pid, /var/run/svnserve(/.*)?
275
276
277       Note:  File context can be temporarily modified with the chcon command.
278       If you want to permanently change the file context you need to use  the
279       semanage fcontext command.  This will modify the SELinux labeling data‐
280       base.  You will need to use restorecon to apply the labels.
281
282

COMMANDS

284       semanage fcontext can also be used to manipulate default  file  context
285       mappings.
286
287       semanage  permissive  can  also  be used to manipulate whether or not a
288       process type is permissive.
289
290       semanage module can also be used to enable/disable/install/remove  pol‐
291       icy modules.
292
293       semanage boolean can also be used to manipulate the booleans
294
295
296       system-config-selinux is a GUI tool available to customize SELinux pol‐
297       icy settings.
298
299

AUTHOR

301       This manual page was auto-generated using sepolicy manpage .
302
303