haproxy_selinux(8)

πŸ“¦
version 20250627+git412.dbf877ab7 Β· 7 versions
, in opensuse-leap 16.0

πŸ’– NAME πŸ’–

okay so bestie, we're looking at haproxy_selinux(8) β€” the SELinux policy that wraps the haproxy processes in a big secure hug. Security-Enhanced Linux, but make it haproxy. πŸ’…


✨ DESCRIPTION ✨

Security-Enhanced Linux secures the haproxy processes via flexible mandatory access control. No cap, it's literally mandatory.

The haproxy processes execute with the haproxy_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier. Like, just peek at their vibe:

ps -eZ | grep haproxy_t

πŸšͺ ENTRYPOINTS πŸšͺ

The haproxy_t SELinux type can be entered via the haproxy_exec_t file type. That's the gateway, the main character energy.

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

  • /usr/bin/haproxy
  • /usr/bin/haproxy-systemd-wrapper

πŸ‘‘ 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. iykyk.

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

The following process types are defined for haproxy:

  • haproxy_t
Note: semanage permissive -a haproxy_t can be used to make the process type haproxy_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So it's like, soft-launching the chaos. 😭

πŸŽ›οΈ BOOLEANS πŸŽ›οΈ

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

  • haproxy_connect_any β€” If you want to determine whether haproxy can connect to all TCP ports, you must turn on the haproxy_connect_any boolean. Disabled by default.
setsebool -P haproxy_connect_any 1
  • cluster_use_execmem β€” If you want to allow cluster administrative cluster domains memcheck-amd64- to use executable memory, you must turn on the cluster_use_execmem boolean. Disabled by default.
setsebool -P cluster_use_execmem 1
  • daemons_dontaudit_scheduling β€” 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
  • fips_mode β€” 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
  • nis_enabled β€” 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

πŸ“ MANAGED FILES πŸ“

The SELinux process type haproxy_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. (DAC is the bouncer at the club, SELinux is the VIP list. Both gotta say yes.)

  • cluster_conf_t
    • /etc/cluster(/.*)?
  • cluster_log
    • (no default paths listed)
  • 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
  • haproxy_tmpfs_t
    • (no default paths listed)
  • haproxy_var_lib_t
    • /var/lib/haproxy(/.*)?
  • haproxy_var_run_t
    • /run/haproxy.stat.*
    • /run/haproxy.sock.*
    • /run/haproxy.pid
  • 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

🏷️ 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. Slay.

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

STANDARD FILE CONTEXT

SELinux defines the file context types for the haproxy, 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 haproxy_exec_t '/srv/haproxy/content(/.*)?'
restorecon -R -v /srv/myhaproxy_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. Regex girlies rise. 🧚

The following file types are defined for haproxy:

  • haproxy_exec_t
    • Set files with the haproxy_exec_t type, if you want to transition an executable to the haproxy_t domain.
    • Paths:
      • /usr/bin/haproxy, /usr/bin/haproxy-systemd-wrapper
  • haproxy_tmpfs_t
    • Set files with the haproxy_tmpfs_t type, if you want to store haproxy files on a tmpfs file system.
  • haproxy_unit_file_t
    • Set files with the haproxy_unit_file_t type, if you want to treat the files as haproxy unit content.
  • haproxy_var_lib_t
    • Set files with the haproxy_var_lib_t type, if you want to store the haproxy files under the /var/lib directory.
  • haproxy_var_log_t
    • Set files with the haproxy_var_log_t type, if you want to treat the data as haproxy var log data, usually stored under the /var/log directory.
  • haproxy_var_run_t
    • Set files with the haproxy_var_run_t type, if you want to store the haproxy files under the /run or /var/run directory.
    • Paths:
      • /run/haproxy.stat.*, /run/haproxy.sock.*, /run/haproxy.pid
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. Don't skip the restorecon step, bestie, or it's giving "I changed the VIP list but forgot to tell the bouncer." πŸ’€

πŸ› οΈ 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 boolean can also be used to manipulate the booleans.
  • system-config-selinux is a GUI tool available to customize SELinux policy settings. For the girlies who prefer a visual. πŸŽ€

πŸ‘€ AUTHOR πŸ‘€

This manual page was auto-generated using sepolicy manpage. Not me being a bot, but also literally. πŸ™ˆ


πŸ”— SEE ALSO πŸ”—

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


stay slay, and remember: this page is from haproxy version 26-10-06 of haproxy_selinux(8). πŸ’…βœ¨

πŸ“¦ where this page comes from