httpd_sy..._selinux(8)

📦
version 20250627+git412.dbf877ab7 · 7 versions
, in opensuse-leap 16.0

🌸 NAME 🌸

httpd_sys_script_selinux(8) — bestie, this is the SELinux Policy page for httpd_sys_script processes. It is literally the manual named httpd_sys_script_selinux, and it is all about keeping those processes in line. 💅

✨ DESCRIPTION ✨

Security-Enhanced Linux secures the httpd_sys_script processes via flexible mandatory access control. So yes, SELinux is out here being the bodyguard with rules. 👑

The httpd_sys_script processes execute with the httpd_sys_script_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_sys_script_t

🚪 ENTRYPOINTS 🚪

The httpd_sys_script_t SELinux type can be entered via the cifs_t, nfs_t, httpd_sys_content_t, httpd_sys_script_exec_t, httpdcontent file types.

The default entrypoint paths for the httpd_sys_script_t domain are the following:

/srv/([^/]*/)?www(/.*)?
/var/www(/.*)?
/etc/htdig(/.*)?
/srv/gallery2(/.*)?
/var/lib/trac(/.*)?
/var/lib/htdig(/.*)?
/var/www/icons(/.*)?
/usr/share/glpi(/.*)?
/usr/share/htdig(/.*)?
/usr/share/drupal.*
/usr/share/z-push(/.*)?
/var/www/svn/conf(/.*)?
/usr/share/icecast(/.*)?
/var/lib/cacti/rra(/.*)?
/usr/share/ntop/html(/.*)?
/usr/share/nginx/html(/.*)?
/usr/share/doc/ghc/html(/.*)?
/usr/share/openca/htdocs(/.*)?
/usr/share/selinux-policy[^/]*/html(/.*)?
/opt/.*.cgi
/usr/.*.cgi
/var/www/[^/]*/cgi-bin(/.*)?
/var/www/perl(/.*)?
/var/www/html/[^/]*/cgi-bin(/.*)?
/usr/lib/cgi-bin(/.*)?
/var/www/cgi-bin(/.*)?
/var/www/svn/hooks(/.*)?
/usr/share/wordpress/.*.php
/usr/local/nagios/sbin(/.*)?
/usr/share/wordpress/wp-includes/.*.php
/usr/share/wordpress-mu/wp-config.php

🧠 PROCESS TYPES 🧠

SELinux defines process types (domains) for each process running on the system.

You can see the context of a process using the -Z option to ps.

Policy governs the access confined processes have to files. SELinux httpd_sys_script policy is very flexible allowing users to setup their httpd_sys_script processes in as secure a method as possible.

The following process types are defined for httpd_sys_script:

  • httpd_sys_script_t
Note: semanage permissive -a httpd_sys_script_t can be used to make the process type httpd_sys_script_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. 👀

🎚️ BOOLEANS 🎚️

SELinux policy is customizable based on least access required. httpd_sys_script policy is extremely flexible and has several booleans that allow you to manipulate the policy and run httpd_sys_script with the tightest access possible.

  • fips_mode — default: enabled ✨. If you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean: setsebool -P fips_mode 1.
  • httpd_builtin_scripting — default: enabled 💖. If you want to allow httpd to use built in scripting (usually php), you must turn on the httpd_builtin_scripting boolean: setsebool -P httpd_builtin_scripting 1.
  • httpd_can_manage_courier_spool — default: disabled 💀. If you want to allow httpd to manage the courier spool sock files, you must turn on the httpd_can_manage_courier_spool boolean: setsebool -P httpd_can_manage_courier_spool 1.
  • httpd_can_network_connect — default: disabled 🙈. If you want to allow HTTPD scripts and modules to connect to the network using TCP, you must turn on the httpd_can_network_connect boolean: setsebool -P httpd_can_network_connect 1.
  • httpd_can_network_connect_db — default: disabled 🫶. If you want to allow HTTPD scripts and modules to connect to databases over the network, you must turn on the httpd_can_network_connect_db boolean: setsebool -P httpd_can_network_connect_db 1.
  • httpd_can_sendmail — default: disabled 📨. If you want to allow http daemon to send mail, you must turn on the httpd_can_sendmail boolean: setsebool -P httpd_can_sendmail 1.
  • httpd_enable_cgi — default: enabled 🌟. If you want to allow httpd cgi support, you must turn on the httpd_enable_cgi boolean: setsebool -P httpd_enable_cgi 1.
  • httpd_enable_homedirs — default: disabled 🏠. If you want to allow httpd to read home directories, you must turn on the httpd_enable_homedirs boolean: setsebool -P httpd_enable_homedirs 1.
  • httpd_execmem — default: disabled 😭. If you want to allow httpd scripts and modules execmem/execstack, you must turn on the httpd_execmem boolean: setsebool -P httpd_execmem 1.
  • httpd_read_user_content — default: disabled 🍓. If you want to allow httpd to read user content, you must turn on the httpd_read_user_content boolean: setsebool -P httpd_read_user_content 1.
  • httpd_ssi_exec — default: disabled 🧚. If you want to allow HTTPD to run SSI executables in the same domain as system CGI scripts, you must turn on the httpd_ssi_exec boolean: setsebool -P httpd_ssi_exec 1.
  • httpd_tmp_exec — default: disabled 💥. If you want to allow Apache to execute tmp content, you must turn on the httpd_tmp_exec boolean: setsebool -P httpd_tmp_exec 1.
  • httpd_unified — default: disabled 🌈. If you want to unify HTTPD handling of all content files, you must turn on the httpd_unified boolean: setsebool -P httpd_unified 1.
  • httpd_use_cifs — default: disabled 💜. If you want to allow httpd to access cifs file systems, you must turn on the httpd_use_cifs boolean: setsebool -P httpd_use_cifs 1.
  • httpd_use_fusefs — default: disabled 🦋. If you want to allow httpd to access FUSE file systems, you must turn on the httpd_use_fusefs boolean: setsebool -P httpd_use_fusefs 1.
  • httpd_use_nfs — default: disabled 🎀. If you want to allow httpd to access nfs file systems, you must turn on the httpd_use_nfs boolean: setsebool -P httpd_use_nfs 1.
  • httpd_use_openstack — default: disabled ☁️. If you want to allow httpd to access openstack ports, you must turn on the httpd_use_openstack boolean: setsebool -P httpd_use_openstack 1.
  • nis_enabled — default: disabled 💫. If you want to allow system to run with NIS, you must turn on the nis_enabled boolean: setsebool -P nis_enabled 1.
  • use_nfs_home_dirs — default: enabled 🏡. If you want to support NFS home directories, you must turn on the use_nfs_home_dirs boolean: setsebool -P use_nfs_home_dirs 1.
  • use_samba_home_dirs — default: disabled 💀. If you want to support SAMBA home directories, you must turn on the use_samba_home_dirs boolean: setsebool -P use_samba_home_dirs 1.

📁 MANAGED FILES 📁

The SELinux process type httpd_sys_script_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. 🔑

  • fusefs_t
/run/user/[0-9]+/gvfs
  • httpd_sys_rw_content_t
/etc/rt(/.*)?
/etc/glpi(/.*)?
/etc/horde(/.*)?
/etc/drupal.*
/etc/z-push(/.*)?
/var/lib/svn(/.*)?
/var/www/svn(/.*)?
/etc/owncloud(/.*)?
/var/www/html(/.*)?/uploads(/.*)?
/var/www/html(/.*)?/wp-content(/.*)?
/var/www/html(/.*)?/wp_backups(/.*)?
/var/www/html(/.*)?/sites/default/files(/.*)?
/var/www/html(/.*)?/sites/default/settings.php
/etc/mock/koji(/.*)?
/etc/nextcloud(/.*)?
/var/lib/drupal.*
/etc/zabbix/web(/.*)?
/var/lib/moodle(/.*)?
/var/log/z-push(/.*)?
/var/spool/gosa(/.*)?
/etc/WebCalendar(/.*)?
/usr/share/joomla(/.*)?
/var/lib/dokuwiki(/.*)?
/var/lib/httpd/md(/.*)?
/var/lib/owncloud(/.*)?
/var/spool/viewvc(/.*)?
/var/lib/nextcloud(/.*)?
/var/lib/pootle/po(/.*)?
/var/lib/phpMyAdmin(/.*)?
/var/www/moodledata(/.*)?
/srv/gallery2/smarty(/.*)?
/var/www/moodle/data(/.*)?
/var/lib/graphite-web(/.*)?
/var/log/shibboleth-www(/.*)?
/var/www/gallery/albums(/.*)?
/var/www/html/owncloud/data(/.*)?
/var/www/html/nextcloud/apps(/.*)?
/var/www/html/nextcloud/data(/.*)?
/var/www/html/nextcloud/config(/.*)?
/usr/share/wordpress-mu/wp-content(/.*)?
/usr/share/wordpress/wp-content/upgrade(/.*)?
/usr/share/wordpress/wp-content/uploads(/.*)?
/var/www/html/configuration.php
  • httpd_tmp_t
/run/user/apache(/.*)?
/var/www/openshift/console/tmp(/.*)?
  • httpdcontent — no paths are listed for this one on this page.
  • hugetlbfs_t
/dev/hugepages
/usr/lib/udev/devices/hugepages
  • krb5_host_rcache_t
/var/tmp/krb5_0.rcache2
/var/cache/krb5rcache(/.*)?
/var/tmp/nfs_0
/var/tmp/DNS_25
/var/tmp/host_0
/var/tmp/imap_0
/var/tmp/HTTP_23
/var/tmp/HTTP_48
/var/tmp/ldap_55
/var/tmp/ldap_487
/var/tmp/ldapmap1_0

🏷️ FILE CONTEXTS 🏷️

SELinux requires files to have an extended attribute to define the file type.

You can see the context of a file using the -Z option to ls.

Policy governs the access confined processes have to these files. SELinux httpd_sys_script policy is very flexible allowing users to setup their httpd_sys_script processes in as secure a method as possible.

🎀 STANDARD FILE CONTEXT 🎀

SELinux defines the file context types for the httpd_sys_script. If you wanted to store files with these types in a different paths, you need to execute the semanage command to specify alternate labeling and then use restorecon to put the labels on disk.

semanage fcontext -a -t httpd_sys_script_exec_t '/srv/httpd_sys_script/content(/.*)?'
restorecon -R -v /srv/myhttpd_sys_script_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. 🧠

The following file types are defined for httpd_sys_script:

  • httpd_sys_script_exec_t — Set files with the httpd_sys_script_exec_t type, if you want to transition an executable to the httpd_sys_script_t domain.

Paths:

/opt/.*.cgi
/usr/.*.cgi
/var/www/[^/]*/cgi-bin(/.*)?
/var/www/perl(/.*)?
/var/www/html/[^/]*/cgi-bin(/.*)?
/usr/lib/cgi-bin(/.*)?
/var/www/cgi-bin(/.*)?
/var/www/svn/hooks(/.*)?
/usr/share/wordpress/.*.php
/usr/local/nagios/sbin(/.*)?
/usr/share/wordpress/wp-includes/.*.php
/usr/share/wordpress-mu/wp-config.php
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. 💖

🦋 SHARING FILES 🦋

Okay bestie, so if you wanna share files with multiple domains — like Apache, FTP, rsync, and Samba — you can set a file context of public_content_t and public_content_rw_t. These contexts allow any of the above domains to read the content. Iconic. But if you want a particular domain to write to the public_content_rw_t domain, you have to set the appropriate boolean. No cap.

So, to allow httpd_sys_script servers to read the /var/httpd_sys_script directory, add the public_content_t file type to the directory and restore the file type:

semanage fcontext -a -t public_content_t "/var/httpd_sys_script(/.*)?"
restorecon -F -R -v /var/httpd_sys_script

And to allow httpd_sys_script servers to read and write /var/httpd_sys_script/incoming, add the public_content_rw_t type to the directory and restore the file type. You also need to turn on the httpd_sys_script_anon_write boolean:

semanage fcontext -a -t public_content_rw_t "/var/httpd_sys_script/incoming(/.*)?"
restorecon -F -R -v /var/httpd_sys_script/incoming
setsebool -P httpd_sys_script_anon_write 1

Now, if you want to allow apache scripts to write to public content, directories/files must be labeled public_rw_content_t., you must turn on the httpd_sys_script_anon_write boolean. Like so:

setsebool -P httpd_sys_script_anon_write 1

💅 COMMANDS 💅

  • semanage fcontext — can also be used to manipulate default file context mappings. Slay.
  • 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.

🎀 AUTHOR 🎀

This manual page was auto-generated using sepolicy manpage .

✨ SEE ALSO ✨

selinux(8), httpd_sys_script(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8)

This page is from httpd_sys_script, dated 26-10-06, and it’s the httpd_sy..._selinux(8) manual page. Byeee, bestie 💖🫶

📦 where this page comes from