varnishd_selinux(8)

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

💅 varnishd_selinux(8) — SELinux Policy varnishd

ok so this is varnishd_selinux, the manual page for the Security Enhanced Linux Policy for the varnishd processes. yes bestie, we're doing SELinux today and honestly? it's giving "complicated but iconic." 🦋

✨ NAME ✨

varnishd_selinux — Security Enhanced Linux Policy for the varnishd processes 🎀

🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the varnishd processes via flexible mandatory access control. like, it's literally the bouncer at the club and it does not let just anyone in. 💅

The varnishd processes execute with the varnishd_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 varnishd_t

see? easy. that's your vibe check right there. 👑

🚪 ENTRYPOINTS 🚪

The varnishd_t SELinux type can be entered via the varnishd_exec_t file type.

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

/usr/bin/varnishd

one path. that's it. that's the door. 🚪✨

🎭 PROCESS TYPES 🎭

SELinux defines process types (domains) for each process running on the system — think of them as little outfits each process wears so the policy knows who it is. 👗

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

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

The following process types are defined for varnishd:

  • varnishd_t
Note: semanage permissive -a varnishd_t can be used to make the process type varnishd_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like… it stops blocking, but it still talks about you behind your back. messy but true. 😭

🔘 BOOLEANS 🔘

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

If you want to determine whether varnishd can use the full TCP network, you must turn on the varnishd_connect_any boolean. Disabled by default.

setsebool -P varnishd_connect_any 1

If you want to dontaudit all daemons scheduling requests (setsched, sys_nice), you must turn on the daemons_dontaudit_scheduling boolean. Enabled by default.

setsebool -P daemons_dontaudit_scheduling 1

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

If you want to allow system to run with NIS, you must turn on the nis_enabled boolean. Disabled by default.

setsebool -P nis_enabled 1

that -P? it means persistent. it survives a reboot. we love commitment. 💖

🔌 PORT TYPES 🔌

SELinux defines port types to represent TCP and UDP ports.

You can see the types associated with a port by using the following command:

semanage port -l

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

The following port types are defined for varnishd:

  • varnishd_port_t

Default Defined Ports:

tcp 6081-6082

two whole ports. generous of her honestly. 🔥

📁 MANAGED FILES 📁

The SELinux process type varnishd_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 — SELinux is not out here overriding the classics, she's layered. 💅

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

/run/crm(/.*)?
/run/cman_.*
/run/rsctmp(/.*)?
/run/aisexec.*
/run/heartbeat(/.*)?
/run/pcsd-ruby.socket
/run/corosync-qnetd(/.*)?
/run/corosync-qdevice(/.*)?
/run/pcsd.socket
/run/corosync.pid
/run/cpglockd.pid
/run/rgmanager.pid
/run/cluster/rgmanager.sk

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

root_t

/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
/var/lib/ntp

varnishd_tmp_t

(no default paths listed for this one — she's a mystery 🕵️‍♀️)

varnishd_var_lib_t

/var/lib/varnish(/.*)?

varnishd_var_run_t

/run/varnish.pid

🏷️ 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 varnishd policy is very flexible allowing users to setup their varnishd processes in as secure a method as possible.

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for the varnishd, 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 varnishd_exec_t '/srv/varnishd/content(/.*)?'
restorecon -R -v /srv/myvarnishd_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex jumpscare, but make it fashion. 🙈

The following file types are defined for varnishd:

  • varnishd_etc_t — Set files with the varnishd_etc_t type, if you want to store varnishd files in the /etc directories.
  • varnishd_exec_t — Set files with the varnishd_exec_t type, if you want to transition an executable to the varnishd_t domain.
  • varnishd_initrc_exec_t — Set files with the varnishd_initrc_exec_t type, if you want to transition an executable to the varnishd_initrc_t domain.
  • varnishd_tmp_t — Set files with the varnishd_tmp_t type, if you want to store varnishd temporary files in the /tmp directories.
  • varnishd_var_lib_t — Set files with the varnishd_var_lib_t type, if you want to store the varnishd files under the /var/lib directory.
  • varnishd_var_run_t — Set files with the varnishd_var_run_t type, if you want to store the varnishd 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. temporary vs permanent is literally the whole plot of this story, don't skip it. 😭

🛠️ COMMANDS 🛠️

  • semanage fcontext can also be used to manipulate default file context mappings.
  • 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 port can also be used to manipulate the port definitions
  • semanage boolean can also be used to manipulate the booleans
  • system-config-selinux is a GUI tool available to customize SELinux policy settings. yes bestie, a GUI. for the girlies who don't vibe with the terminal (no judgment, we love you). 🎀

👑 AUTHOR 👑

This manual page was auto-generated using sepolicy manpage .

🦋 SEE ALSO 🦋

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

and that's the whole page, bestie — go forth and label things correctly 💖✨

this iconic little number came from the varnishd manual, dated 26-10-06, and it's officially varnishd_selinux(8). mwah. 💋

📦 where this page comes from