1varnishlog_selinux(8) SELinux Policy varnishlog varnishlog_selinux(8)
2
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 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 For example:
18 ps -eZ | grep varnishlog_t
20
24 The varnishlog_t SELinux type can be entered via the varnishlog_exec_t
25 file type.
26 The default entrypoint paths for the varnishlog_t domain are the fol‐
28 lowing:
29 /usr/bin/varnishlog, /usr/bin/varnishncsa
31
33 SELinux defines process types (domains) for each process running on the
34 system
35 You can see the context of a process using the -Z option to ps
37 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 The following process types are defined for varnishlog:
43 varnishlog_t
45 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
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 If you want to allow all domains to execute in fips_mode, you must turn
61 on the fips_mode boolean. Enabled by default.
62 setsebool -P fips_mode 1
64
68 The SELinux process type varnishlog_t can manage files labeled with the
69 following file types. The paths listed are the default paths for these
70 file types. Note the processes UID still need to have DAC permissions.
71 cluster_conf_t
73 /etc/cluster(/.*)?
75 cluster_var_lib_t
77 /var/lib/pcsd(/.*)?
79 /var/lib/cluster(/.*)?
80 /var/lib/openais(/.*)?
81 /var/lib/pengine(/.*)?
82 /var/lib/corosync(/.*)?
83 /usr/lib/heartbeat(/.*)?
84 /var/lib/heartbeat(/.*)?
85 /var/lib/pacemaker(/.*)?
86 cluster_var_run_t
88 /var/run/crm(/.*)?
90 /var/run/cman_.*
91 /var/run/rsctmp(/.*)?
92 /var/run/aisexec.*
93 /var/run/heartbeat(/.*)?
94 /var/run/corosync-qnetd(/.*)?
95 /var/run/corosync-qdevice(/.*)?
96 /var/run/corosync.pid
97 /var/run/cpglockd.pid
98 /var/run/rgmanager.pid
99 /var/run/cluster/rgmanager.sk
100 root_t
102 /sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
104 /
105 /initrd
106 varnishlog_var_run_t
108 /var/run/varnishlog.pid
110 /var/run/varnishncsa.pid
111
114 SELinux requires files to have an extended attribute to define the file
115 type.
116 You can see the context of a file using the -Z option to ls
118 Policy governs the access confined processes have to these files.
120 SELinux varnishlog policy is very flexible allowing users to setup
121 their varnishlog processes in as secure a method as possible.
122 STANDARD FILE CONTEXT
124 SELinux defines the file context types for the varnishlog, if you
126 wanted to store files with these types in a diffent paths, you need to
127 execute the semanage command to sepecify alternate labeling and then
128 use restorecon to put the labels on disk.
129 semanage fcontext -a -t varnishlog_log_t '/srv/myvarnishlog_con‐
131 tent(/.*)?'
132 restorecon -R -v /srv/myvarnishlog_content
133 Note: SELinux often uses regular expressions to specify labels that
135 match multiple files.
136 The following file types are defined for varnishlog:
138 varnishlog_exec_t
142 - Set files with the varnishlog_exec_t type, if you want to transition
144 an executable to the varnishlog_t domain.
145 Paths:
148 /usr/bin/varnishlog, /usr/bin/varnishncsa
149 varnishlog_initrc_exec_t
152 - Set files with the varnishlog_initrc_exec_t type, if you want to
154 transition an executable to the varnishlog_initrc_t domain.
155 Paths:
158 /etc/rc.d/init.d/varnishlog, /etc/rc.d/init.d/varnishncsa
159 varnishlog_log_t
162 - Set files with the varnishlog_log_t type, if you want to treat the
164 data as varnishlog log data, usually stored under the /var/log direc‐
165 tory.
166 varnishlog_var_run_t
170 - Set files with the varnishlog_var_run_t type, if you want to store
172 the varnishlog files under the /run or /var/run directory.
173 Paths:
176 /var/run/varnishlog.pid, /var/run/varnishncsa.pid
177 Note: File context can be temporarily modified with the chcon command.
180 If you want to permanently change the file context you need to use the
181 semanage fcontext command. This will modify the SELinux labeling data‐
182 base. You will need to use restorecon to apply the labels.
183
186 semanage fcontext can also be used to manipulate default file context
187 mappings.
188 semanage permissive can also be used to manipulate whether or not a
190 process type is permissive.
191 semanage module can also be used to enable/disable/install/remove pol‐
193 icy modules.
194 semanage boolean can also be used to manipulate the booleans
196 system-config-selinux is a GUI tool available to customize SELinux pol‐
199 icy settings.
200
203 This manual page was auto-generated using sepolicy manpage .
204
207 selinux(8), varnishlog(8), semanage(8), restorecon(8), chcon(1), sepol‐
208 icy(8), setsebool(8)
209varnishlog 19-06-18 varnishlog_selinux(8)