Security-Enhanced Linux secures the httpd_rotatelogs processes via flexible mandatory access control.
The httpd_rotatelogs processes execute with the httpd_rotatelogs_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 httpd_rotatelogs_t
The httpd_rotatelogs_t SELinux type can be entered via the httpd_rotatelogs_exec_t file type.
The default entrypoint paths for the httpd_rotatelogs_t domain are the following:
You can see the context of a process using the -Z option to psP Policy governs the access confined processes have to files. SELinux httpd_rotatelogs policy is very flexible allowing users to setup their httpd_rotatelogs processes in as secure a method as possible.
The following process types are defined for httpd_rotatelogs:
httpd_rotatelogs_t
Note: semanage permissive -a httpd_rotatelogs_t can be used to make the process type httpd_rotatelogs_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 httpd_rotatelogs_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
httpd_log_t
/srv/([^/]*/)?www/logs(/.*)?
/var/www(/.*)?/logs(/.*)?
/var/log/glpi(/.*)?
/var/log/cacti(/.*)?
/var/log/httpd(/.*)?
/var/log/nginx(/.*)?
/var/log/apache(2)?(/.*)?
/var/log/horizon(/.*)?
/var/log/php-fpm(/.*)?
/var/log/cherokee(/.*)?
/var/log/lighttpd(/.*)?
/var/log/suphp.log.*
/var/log/thttpd.log.*
/var/log/apache-ssl(2)?(/.*)?
/var/log/cgiwrap.log.*
/var/www/stickshift/[^/]*/log(/.*)?
/var/log/graphite-web(/.*)?
/var/www/miq/vmdb/log(/.*)?
/var/log/roundcubemail(/.*)?
/var/log/php_errors.log.*
/var/log/dirsrv/admin-serv(/.*)?
/var/opt/rh/rh-nginx18/log(/.*)?
/var/lib/openshift/.log/httpd(/.*)?
/var/www/openshift/console/log(/.*)?
/var/www/openshift/broker/httpd/logs(/.*)?
/var/www/openshift/console/httpd/logs(/.*)?
/etc/httpd/logs
root_t
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
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 httpd_rotatelogs policy is very flexible allowing users to setup their httpd_rotatelogs processes in as secure a method as possible.
The following file types are defined for httpd_rotatelogs:
httpd_rotatelogs_exec_t
- Set files with the httpd_rotatelogs_exec_t type, if you want to transition an executable to the httpd_rotatelogs_t domain.
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.