Security-Enhanced Linux secures the varnishlog processes via flexible mandatory access control.
The varnishlog processes execute with the varnishlog_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier.
For example:
ps -eZ | grep varnishlog_t
The varnishlog_t SELinux type can be entered via the varnishlog_exec_t file type.
The default entrypoint paths for the varnishlog_t domain are the following:
/usr/bin/varnishlog, /usr/bin/varnishncsa
You can see the context of a process using the -Z option to psP Policy governs the access confined processes have to files. SELinux varnishlog policy is very flexible allowing users to setup their varnishlog processes in as secure a method as possible.
The following process types are defined for varnishlog:
varnishlog_t
Note: semanage permissive -a varnishlog_t can be used to make the process type varnishlog_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated.
If you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean. Enabled by default.
setsebool -P fips_mode 1
The SELinux process type varnishlog_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. Note the processes UID still need to have DAC permissions.
cluster_conf_t
/etc/cluster(/.*)?
cluster_var_lib_t
/var/lib/pcsd(/.*)?
/var/lib/cluster(/.*)?
/var/lib/openais(/.*)?
/var/lib/pengine(/.*)?
/var/lib/corosync(/.*)?
/usr/lib/heartbeat(/.*)?
/var/lib/heartbeat(/.*)?
/var/lib/pacemaker(/.*)?
cluster_var_run_t
/var/run/crm(/.*)?
/var/run/cman_.*
/var/run/rsctmp(/.*)?
/var/run/aisexec.*
/var/run/heartbeat(/.*)?
/var/run/corosync-qnetd(/.*)?
/var/run/corosync-qdevice(/.*)?
/var/run/corosync.pid
/var/run/cpglockd.pid
/var/run/rgmanager.pid
/var/run/cluster/rgmanager.sk
root_t
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
varnishlog_var_run_t
/var/run/varnishlog.pid
/var/run/varnishncsa.pid
You can see the context of a file using the -Z option to lsP Policy governs the access confined processes have to these files. SELinux varnishlog policy is very flexible allowing users to setup their varnishlog processes in as secure a method as possible.
STANDARD FILE CONTEXT
SELinux defines the file context types for the varnishlog, if you wanted to store files with these types in a diffent paths, you need to execute the semanage command to sepecify alternate labeling and then use restorecon to put the labels on disk.
semanage fcontext -a -t varnishlog_log_t '/srv/myvarnishlog_content(/.*)?'
restorecon -R -v /srv/myvarnishlog_content
Note: SELinux often uses regular expressions to specify labels that match multiple files.
The following file types are defined for varnishlog:
varnishlog_exec_t
- Set files with the varnishlog_exec_t type, if you want to transition an executable to the varnishlog_t domain.
varnishlog_initrc_exec_t
- Set files with the varnishlog_initrc_exec_t type, if you want to transition an executable to the varnishlog_initrc_t domain.
varnishlog_log_t
- Set files with the varnishlog_log_t type, if you want to treat the data as varnishlog log data, usually stored under the /var/log directory.
varnishlog_var_run_t
- Set files with the varnishlog_var_run_t type, if you want to store the varnishlog files under the /run or /var/run directory.
Note: File context can be temporarily modified with the chcon command. If you want to permanently change the file context you need to use the semanage fcontext command. This will modify the SELinux labeling database. You will need to use restorecon to apply the labels.
semanage permissive can also be used to manipulate whether or not a process type is permissive.
semanage module can also be used to enable/disable/install/remove policy modules.
semanage boolean can also be used to manipulate the booleans
system-config-selinux is a GUI tool available to customize SELinux policy settings.