systemd_l...r_selinux(8)

💖 NAME 💖

Welcome to systemd_l...r_selinux(8) — yes bestie, that’s the manual name — aka the SELinux Policy page for systemd_logger.

systemd_logger_selinux — Security Enhanced Linux Policy for the systemd_logger processes. Periodt. 💅

---

✨ DESCRIPTION ✨

Security-Enhanced Linux secures the systemd_logger processes via flexible mandatory access control. That’s the whole vibe: mandatory access control, but make it flexible. 🦋

The systemd_logger processes execute with the systemd_logger_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 systemd_logger_t

---

🎀 ENTRYPOINTS 🎀

The systemd_logger_t SELinux type can be entered via the systemd_logger_exec_t file type. Iconic little doorway, honestly. 🚪✨

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

/usr/lib/systemd/systemd-logger

---

👑 PROCESS TYPES 👑

SELinux defines process types (domains) for each process running on the system. Very main-character energy for every process, ngl. 💜

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

The following process types are defined for systemd_logger:

systemd_logger_t

Note: semanage permissive -a systemd_logger_t can be used to make the process type systemd_logger_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So like… permissive, not invisible. 🤨💀

---

🌈 BOOLEANS 🌈

SELinux policy is customizable based on least access required. systemd_logger policy is extremely flexible and has several booleans that allow you to manipulate the policy and run systemd_logger with the tightest access possible. Tightest access possible = the friend who brings exactly one snack to the group chat and somehow it’s enough. 🍓

• 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

---

🦋 MANAGED FILES 🦋

The SELinux process type systemd_logger_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. Note that the processes UID still need to have DAC permissions. DAC permissions stay relevant, bestie — SELinux is not out here doing everything alone. 😌

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. Fancy little file accessory, but make it security. 🎀

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

🧚 STANDARD FILE CONTEXT 🧚

SELinux defines the file context types for the systemd_logger, 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 systemd_logger_exec_t '/srv/systemd_logger/content(/.*)?'
restorecon -R -v /srv/mysystemd_logger_content

Note: SELinux often uses regular expressions to specify labels that match multiple files. Regex girlies stay winning. 🔥

The following file types are defined for systemd_logger:

systemd_logger_exec_t

• Set files with the systemd_logger_exec_t type, if you want to transition an executable to the systemd_logger_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.

---

🌸 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.

---

🫶 AUTHOR 🫶

This manual page was auto-generated using sepolicy manpage .

---

💜 SEE ALSO 💜

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

---

Cute little footer tea ☕: this page is from the systemd_logger source/version, dated 26-10-06, and its manual name is systemd_l...r_selinux(8). That’s the sign-off, bestie — stay labeled and slay. 💖✨