system...selinux(8)

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

💅 systemd_user_runtimedir_selinux — the manual page, but make it bestie-friendly 💅

Okay so bestie, this is the systemd_user_runtimedir_selinux(8) page — yes, section 8, the big-girl admin section — and it's all about the SELinux policy for the systemd_user_runtimedir processes. Grab a lil' drink, we're getting into it. 🫶

🌸 NAME 🌸

systemd_user_runtimedir_selinux — Security Enhanced Linux Policy for the systemd_user_runtimedir processes. That's it, that's the whole name. Iconic, lowkey. ✨

🦋 DESCRIPTION 🦋

Security-Enhanced Linux secures the systemd_user_runtimedir processes via flexible mandatory access control. No cap, MAC is literally the whole vibe here — it's the bouncer at the club, and every process needs its name on the list.

The systemd_user_runtimedir processes execute with the systemd_user_runtimedir_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier. So like:

ps -eZ | grep systemd_user_runtimedir_t

That's the whole check. Slay. 💖

✨ ENTRYPOINTS ✨

So you wanna know how a process gets into this domain? The systemd_user_runtimedir_t SELinux type can be entered via the systemd_user_runtimedir_exec_t file type. It's giving "VIP entrance only."

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

/usr/lib/systemd/systemd-user-runtime-dir

One path. One. She's exclusive. 🎀

👑 PROCESS TYPES 👑

SELinux defines process types (domains) for each process running on the system. We love a structured queen. 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_user_runtimedir policy is very flexible allowing users to setup their systemd_user_runtimedir processes in as secure a method as possible. Flexible but firm — main character energy.

The following process types are defined for systemd_user_runtimedir:

  • systemd_user_runtimedir_t
Note: semanage permissive -a systemd_user_runtimedir_t can be used to make the process type systemd_user_runtimedir_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So like, she's off the hook but the receipts still exist. 🙈

💀 BOOLEANS 💀

SELinux policy is customizable based on least access required — the "you get nothing until you ask nicely" philosophy. systemd_user_runtimedir policy is extremely flexible and has several booleans that allow you to manipulate the policy and run systemd_user_runtimedir with the tightest access possible. Tightest. Access. Possible. Periodt.

  • 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

Not me listing every single one. But that's the job. 💅

🍓 MANAGED FILES 🍓

The SELinux process type systemd_user_runtimedir_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 don't override regular permissions, she just adds a whole extra layer of no. 😭

  • 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

Every path, every wildcard, every regex — untouched. I would never do you dirty like that bestie. 🌈

🧚 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_user_runtimedir policy is very flexible allowing users to setup their systemd_user_runtimedir processes in as secure a method as possible. We stan a customizable queen.

💜 STANDARD FILE CONTEXT 💜

SELinux defines the file context types for the systemd_user_runtimedir, 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 so:

semanage fcontext -a -t systemd_user_runtimedir_exec_t '/srv/systemd_user_runtimedir/content(/.*)?'
restorecon -R -v /srv/mysystemd_user_runtimedir_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. Regex girlies rise. 🦋

The following file types are defined for systemd_user_runtimedir:

  • systemd_user_runtimedir_exec_t — Set files with the systemd_user_runtimedir_exec_t type, if you want to transition an executable to the systemd_user_runtimedir_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. Temporary vs permanent — choose wisely babe. ⭐

🔥 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 GUI girlies and the CLI besties. Both valid. 💅

🫶 AUTHOR 🫶

This manual page was auto-generated using sepolicy manpage. A bot wrote this and honestly? She ate. 🔥

🌟 SEE ALSO 🌟

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

Go read them. Or don't. I'm a manpage, not a cop. 😌

Sign-off: This was systemd_user_runtimedir from the system...selinux(8) manual, dated 26-10-06. Thanks for coming to my TED talk, bestie. Now go run ps -eZ | grep systemd_user_runtimedir_t and tell me what you find. 💖✨🎀
📦 where this page comes from