1varnishlog_selinux(8) SELinux Policy varnishlog varnishlog_selinux(8)
2
3
4
6 varnishlog_selinux - Security Enhanced Linux Policy for the varnishlog
7 processes
8
10 Security-Enhanced Linux secures the varnishlog processes via flexible
11 mandatory access control.
12
13 The varnishlog processes execute with the varnishlog_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 varnishlog_t
20
21
22
24 The varnishlog_t SELinux type can be entered via the varnishlog_exec_t
25 file type.
26
27 The default entrypoint paths for the varnishlog_t domain are the fol‐
28 lowing:
29
30 /usr/bin/varnishlog, /usr/bin/varnisncsa
31
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 varnishlog policy is very flexible allowing users to setup their var‐
40 nishlog processes in as secure a method as possible.
41
42 The following process types are defined for varnishlog:
43
44 varnishlog_t
45
46 Note: semanage permissive -a varnishlog_t can be used to make the
47 process type varnishlog_t permissive. SELinux does not deny access to
48 permissive process types, but the AVC (SELinux denials) messages are
49 still generated.
50
51
53 SELinux policy is customizable based on least access required. var‐
54 nishlog policy is extremely flexible and has several booleans that
55 allow you to manipulate the policy and run varnishlog with the tightest
56 access possible.
57
58
59
60 If you want to allow all daemons to write corefiles to /, you must turn
61 on the allow_daemons_dump_core boolean. Disabled by default.
62
63 setsebool -P allow_daemons_dump_core 1
64
65
66
67 If you want to allow all daemons to use tcp wrappers, you must turn on
68 the allow_daemons_use_tcp_wrapper boolean. Disabled by default.
69
70 setsebool -P allow_daemons_use_tcp_wrapper 1
71
72
73
74 If you want to allow all daemons the ability to read/write terminals,
75 you must turn on the allow_daemons_use_tty boolean. Disabled by
76 default.
77
78 setsebool -P allow_daemons_use_tty 1
79
80
81
82 If you want to allow all domains to use other domains file descriptors,
83 you must turn on the allow_domain_fd_use boolean. Enabled by default.
84
85 setsebool -P allow_domain_fd_use 1
86
87
88
89 If you want to allow sysadm to debug or ptrace all processes, you must
90 turn on the allow_ptrace boolean. Disabled by default.
91
92 setsebool -P allow_ptrace 1
93
94
95
96 If you want to enable cluster mode for daemons, you must turn on the
97 daemons_enable_cluster_mode boolean. Disabled by default.
98
99 setsebool -P daemons_enable_cluster_mode 1
100
101
102
103 If you want to allow all domains to have the kernel load modules, you
104 must turn on the domain_kernel_load_modules boolean. Disabled by
105 default.
106
107 setsebool -P domain_kernel_load_modules 1
108
109
110
111 If you want to allow all domains to execute in fips_mode, you must turn
112 on the fips_mode boolean. Enabled by default.
113
114 setsebool -P fips_mode 1
115
116
117
118 If you want to enable reading of urandom for all domains, you must turn
119 on the global_ssp boolean. Disabled by default.
120
121 setsebool -P global_ssp 1
122
123
124
125 If you want to enable support for upstart as the init program, you must
126 turn on the init_upstart boolean. Enabled by default.
127
128 setsebool -P init_upstart 1
129
130
131
133 The SELinux process type varnishlog_t can manage files labeled with the
134 following file types. The paths listed are the default paths for these
135 file types. Note the processes UID still need to have DAC permissions.
136
137 cluster_conf_t
138
139 /etc/cluster(/.*)?
140
141 cluster_var_lib_t
142
143 /var/lib(64)?/openais(/.*)?
144 /var/lib(64)?/pengine(/.*)?
145 /var/lib(64)?/corosync(/.*)?
146 /usr/lib(64)?/heartbeat(/.*)?
147 /var/lib(64)?/heartbeat(/.*)?
148 /var/lib(64)?/pacemaker(/.*)?
149 /var/lib/cluster(/.*)?
150
151 cluster_var_run_t
152
153 /var/run/crm(/.*)?
154 /var/run/cman_.*
155 /var/run/rsctmp(/.*)?
156 /var/run/aisexec.*
157 /var/run/heartbeat(/.*)?
158 /var/run/cpglockd.pid
159 /var/run/corosync.pid
160 /var/run/rgmanager.pid
161 /var/run/cluster/rgmanager.sk
162
163 initrc_tmp_t
164
165
166 mnt_t
167
168 /mnt(/[^/]*)
169 /mnt(/[^/]*)?
170 /rhev(/[^/]*)?
171 /media(/[^/]*)
172 /media(/[^/]*)?
173 /etc/rhgb(/.*)?
174 /media/.hal-.*
175 /net
176 /afs
177 /rhev
178 /misc
179
180 root_t
181
182 /
183 /initrd
184
185 tmp_t
186
187 /tmp
188 /usr/tmp
189 /var/tmp
190 /tmp-inst
191 /var/tmp-inst
192 /var/tmp/vi.recover
193
194 varnishlog_log_t
195
196 /var/log/varnish(/.*)?
197
198 varnishlog_var_run_t
199
200 /var/run/varnishlog.pid
201 /var/run/varnishncsa.pid
202
203
205 SELinux requires files to have an extended attribute to define the file
206 type.
207
208 You can see the context of a file using the -Z option to ls
209
210 Policy governs the access confined processes have to these files.
211 SELinux varnishlog policy is very flexible allowing users to setup
212 their varnishlog processes in as secure a method as possible.
213
214 STANDARD FILE CONTEXT
215
216 SELinux defines the file context types for the varnishlog, if you
217 wanted to store files with these types in a diffent paths, you need to
218 execute the semanage command to sepecify alternate labeling and then
219 use restorecon to put the labels on disk.
220
221 semanage fcontext -a -t varnishlog_var_run_t '/srv/myvarnishlog_con‐
222 tent(/.*)?'
223 restorecon -R -v /srv/myvarnishlog_content
224
225 Note: SELinux often uses regular expressions to specify labels that
226 match multiple files.
227
228 The following file types are defined for varnishlog:
229
230
231
232 varnishlog_exec_t
233
234 - Set files with the varnishlog_exec_t type, if you want to transition
235 an executable to the varnishlog_t domain.
236
237
238 Paths:
239 /usr/bin/varnishlog, /usr/bin/varnisncsa
240
241
242 varnishlog_initrc_exec_t
243
244 - Set files with the varnishlog_initrc_exec_t type, if you want to
245 transition an executable to the varnishlog_initrc_t domain.
246
247
248 Paths:
249 /etc/rc.d/init.d/varnishlog, /etc/rc.d/init.d/varnishncsa
250
251
252 varnishlog_log_t
253
254 - Set files with the varnishlog_log_t type, if you want to treat the
255 data as varnishlog log data, usually stored under the /var/log direc‐
256 tory.
257
258
259
260 varnishlog_var_run_t
261
262 - Set files with the varnishlog_var_run_t type, if you want to store
263 the varnishlog files under the /run or /var/run directory.
264
265
266 Paths:
267 /var/run/varnishlog.pid, /var/run/varnishncsa.pid
268
269
270 Note: File context can be temporarily modified with the chcon command.
271 If you want to permanently change the file context you need to use the
272 semanage fcontext command. This will modify the SELinux labeling data‐
273 base. You will need to use restorecon to apply the labels.
274
275
277 semanage fcontext can also be used to manipulate default file context
278 mappings.
279
280 semanage permissive can also be used to manipulate whether or not a
281 process type is permissive.
282
283 semanage module can also be used to enable/disable/install/remove pol‐
284 icy modules.
285
286 semanage boolean can also be used to manipulate the booleans
287
288
289 system-config-selinux is a GUI tool available to customize SELinux pol‐
290 icy settings.
291
292
294 This manual page was auto-generated using sepolicy manpage .
295
296
298 selinux(8), varnishlog(8), semanage(8), restorecon(8), chcon(1) , set‐
299 sebool(8)
300
301
302
303varnishlog 15-06-03 varnishlog_selinux(8)