SYSTEMD_SOCKET_PROXYD_SELINUX(8)

💅 systemd_socket_proxyd_selinux — a girl's guide to keeping your processes in check ✨

okay so bestie, buckle up because we're talking about systemd_socket_proxyd_selinux(8) and honestly? it's giving security realness 🎀 this is the SELinux policy manual for the systemd_socket_proxyd processes and i promise it's less scary than it sounds.

---

🌸 NAME 🌸

systemd_socket_proxyd_selinux — it's literally the Security Enhanced Linux Policy for the systemd_socket_proxyd processes, no cap 💖

---

✨ DESCRIPTION ✨

so Security-Enhanced Linux secures the systemd_socket_proxyd processes via flexible mandatory access control. that's the whole vibe — MAC (mandatory access control, not the makeup, tho both are iconic) keeping everything locked down 🦋

the systemd_socket_proxyd processes execute with the systemd_socket_proxyd_t SELinux type. you can check if you have these processes running by executing the ps command with the -Z qualifier, like so:

ps -eZ | grep systemd_socket_proxyd_t

literally just run that and you'll see what's up 👑

---

🚪 ENTRYPOINTS 🚪

the systemd_socket_proxyd_t SELinux type can be entered via the systemd_socket_proxyd_exec_t file type. that's the doorway bestie, the main character entrance 💅

the default entrypoint paths for the systemd_socket_proxyd_t domain are the following:

/usr/lib/systemd/systemd-socket-proxyd

one path, one icon, periodt ✨

---

👯 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 systemd_socket_proxyd policy is very flexible allowing users to setup their systemd_socket_proxyd processes in as secure a method as possible 🫶

the following process types are defined for systemd_socket_proxyd:

systemd_socket_proxyd_t

Note: semanage permissive -a systemd_socket_proxyd_t can be used to make the process type systemd_socket_proxyd_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, it's chill but it's still snitching to the logs 😭

---

🎛️ BOOLEANS 🎛️

SELinux policy is customizable based on least access required — the "you get exactly what you need and nothing more" energy we love to see 🌈 and systemd_socket_proxyd policy is extremely flexible and has several booleans that allow you to manipulate the policy and run systemd_socket_proxyd with the tightest access possible.

• if you want to allow systemd-socket-proxyd to bind any port instead of one labelled with systemd_socket_proxyd_port_t, you must turn on the systemd_socket_proxyd_bind_any boolean. Disabled by default.

setsebool -P systemd_socket_proxyd_bind_any 1

• if you want to allow systemd-socket-proxyd to connect to any port instead of labelled ones, you must turn on the systemd_socket_proxyd_connect_any boolean. Disabled by default.

setsebool -P systemd_socket_proxyd_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

---

🔌 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 systemd_socket_proxyd policy is very flexible allowing users to setup their systemd_socket_proxyd processes in as secure a method as possible 💜

the following port types are defined for systemd_socket_proxyd:

systemd_socket_proxyd_port_t

---

📂 MANAGED FILES 📂

the SELinux process type systemd_socket_proxyd_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, so like, SELinux is doing its part but your user perms still matter too, iykyk 🙈

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

---

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

🌟 STANDARD FILE CONTEXT 🌟

SELinux defines the file context types for the systemd_socket_proxyd. 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. like this:

semanage fcontext -a -t systemd_socket_proxyd_exec_t '/srv/systemd_socket_proxyd/content(/.*)?'
restorecon -R -v /srv/mysystemd_socket_proxyd_content

Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies rise up 🧚

the following file types are defined for systemd_socket_proxyd:

systemd_socket_proxyd_exec_t

• set files with the systemd_socket_proxyd_exec_t type, if you want to transition an executable to the systemd_socket_proxyd_t domain.

systemd_socket_proxyd_unit_file_t

• set files with the systemd_socket_proxyd_unit_file_t type, if you want to treat the files as systemd socket proxyd unit content.

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 fix vs permanent slay — choose wisely 💅

---

🛠️ 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 — for the girlies who prefer a lil visual moment 🎀

---

✍️ AUTHOR ✍️

this manual page was auto-generated using sepolicy manpage. the robots did this one, not me 💀

---

👀 SEE ALSO 👀

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

---

okay that's the whole thing bestie, you ate that reading session 💖 this was systemd_socket_proxyd from the systemd..._selinux(8) fam, dropping on 26-10-06 — go forth and secure your processes, you've got this fr fr 🌈👑🦋