systemd...selinux(8)

👑 systemd...selinux(8) — the SELinux Policy for systemd_modules_load tea 🫖

okay so bestie, welcome to the manual page for the SELinux policy that wraps around the systemd_modules_load processes. it lives in the SELinux Policy systemd_modules_load family and honestly? it's giving security gatekeeper energy. let's get into it ✨

---

💖 NAME 💖

systemd_modules_load_selinux — literally the Security Enhanced Linux Policy for the systemd_modules_load processes. that's the whole vibe. 🎀

---

🌸 DESCRIPTION 🌸

so, Security-Enhanced Linux secures the systemd_modules_load processes via flexible mandatory access control. yes, mandatory. it doesn't ask, it just enforces. main character energy fr fr 💅

the systemd_modules_load processes execute with the systemd_modules_load_t SELinux type. wanna check if you've got these processes running? just run the ps command with the -Z qualifier. iconic.

for example:

ps -eZ | grep systemd_modules_load_t

that's it. that's the check. 🔍

---

🦋 ENTRYPOINTS 🦋

here's the thing: the systemd_modules_load_t SELinux type can be entered via the systemd_modules_load_exec_t file type. one door, one key, iykyk 🗝️

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

/usr/lib/systemd/systemd-modules-load

that's the spot. no cap. 📍

---

⭐ PROCESS TYPES ⭐

SELinux defines process types (domains) for each process running on the system. yes, every process gets a little label. we love a system that keeps track of everyone 🙈

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

policy governs the access confined processes have to files. the SELinux systemd_modules_load policy is very flexible, allowing users to setup their systemd_modules_load processes in as secure a method as possible. flexible and secure, we stan 💜

the following process types are defined for systemd_modules_load:

systemd_modules_load_t

Note: semanage permissive -a systemd_modules_load_t can be used to make the process type systemd_modules_load_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like… it won't block you, but it will take notes 📝👀

---

✨ BOOLEANS ✨

SELinux policy is customizable based on least access required. the systemd_modules_load policy is extremely flexible and has several booleans that allow you to manipulate the policy and run systemd_modules_load with the tightest access possible. toggles on toggles, bestie 🎛️

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

if you want to disable kernel module loading, you must turn on the secure_mode_insmod boolean. disabled by default.

setsebool -P secure_mode_insmod 1

side note: that -P is doing a lot of heavy lifting — these are getting written into the persistent policy, so choose your booleans wisely 🫶

---

🧚 MANAGED FILES 🧚

the SELinux process type systemd_modules_load_t can manage files labeled with the following file types. the paths listed are the default paths for these file types. and hey — the process's UID still needs to have DAC permissions. SELinux isn't out here overriding DAC, that's not how this works, bestie 💀

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

tracefs_t

/sys/kernel/tracing

that's a lot of paths and honestly? every single one of them matters. don't skip a line 💜

---

🌈 FILE CONTEXTS 🌈

SELinux requires files to have an extended attribute to define the file type. yes, a whole extra attribute. it's giving ✨organized✨

you can see the context of a file using the -Z option to ls.

policy governs the access confined processes have to these files. the SELinux systemd_modules_load policy is very flexible, allowing users to setup their systemd_modules_load processes in as secure a method as possible. we love a flexible queen 👑

🎀 STANDARD FILE CONTEXT 🎀

SELinux defines the file context types for the systemd_modules_load. 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. two steps, no shortcuts 💅

semanage fcontext -a -t systemd_modules_load_exec_t '/srv/systemd_modules_load/content(/.*)?'
restorecon -R -v /srv/mysystemd_modules_load_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_modules_load:

• systemd_modules_load_exec_t — set files with the systemd_modules_load_exec_t type, if you want to transition an executable to the systemd_modules_load_t domain. 🚪➡️👑
• systemd_modules_load_unit_file_t — set files with the systemd_modules_load_unit_file_t type, if you want to treat the files as systemd modules load 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. and then you will need to use restorecon to apply the labels. temporary vs permanent is a whole thing, don't mix them up 😭

---

💀 COMMANDS 💀

here's your toolbox, bestie — these are the commands that also get the job done:

• 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. yes, a GUI. for the visual learners 🖱️✨

---

🍓 AUTHOR 🍓

this manual page was auto-generated using sepolicy manpage. so nobody hand-wrote this and honestly that's kind of iconic of it 🤖💖

---

🦄 SEE ALSO 🦄

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

go read those next, bestie, they're all linked lore 📚

---

and that's the whole page! 🎉 this one was dated 26-10-06 and shipped under the systemd_modules_load name — catch you in the next manpage, mwah 💋💖