run_init_selinux(8)

💅 run_init_selinux(8) — the whole SELinux vibe check for run_init ✨

okay bestie, so this is the run_init_selinux manual page, part of the SELinux Policy for run_init — yes that's the manual name, we're folding it in right here at the top because we're cute like that 🎀

---

✨ NAME ✨

run_init_selinux — the Security Enhanced Linux Policy for the run_init processes, periodt 💅

---

🦋 DESCRIPTION 🦋

Security-Enhanced Linux secures the run_init processes via flexible mandatory access control. Like, it's the bouncer at the club and it does not let just anyone in 💀

The run_init processes execute with the run_init_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 run_init_t

go off, grep 👑

---

🌈 ENTRYPOINTS 🌈

The run_init_t SELinux type can be entered via the run_init_exec_t file type.

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

• /usr/bin/run_init

that's it, that's the whole guest list 🫶

---

👑 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 run_init policy is very flexible — it lets users set up their run_init processes in as secure a method as possible.

The following process types are defined for run_init:

• run_init_t

Note: semanage permissive -a run_init_t can be used to make the process type run_init_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So like… it's not a free pass, the receipts still show up 😭

---

🍓 BOOLEANS 🍓

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

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 run_init_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 isn't doing everything for you, bestie 🙈

💜 faillog_t

/var/log/btmp.*
/run/faillock(/.*)?
/var/log/faillog.*
/var/log/tallylog.*

💜 initrc_var_run_t

/run/sysconfig(/.*)?
/run/utmp
/run/keymap
/run/numlock-on
/run/setleds-on
/run/runlevel.dir
/run/setmixer_flag
/run/bootsplashctl

💜 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

💜 security_t

/selinux

---

🌸 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 run_init policy is very flexible, allowing users to set up their run_init processes in as secure a method as possible.

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for the run_init. If you wanted to store files with these types in different paths, you need to execute the semanage command to specify alternate labeling, and then use restorecon to put the labels on disk. it's giving "label it, then commit the label" 💅

semanage fcontext -a -t run_init_exec_t '/srv/run_init/content(/.*)?'
restorecon -R -v /srv/myrun_init_content

Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies, this one's for you 🎀

The following file types are defined for run_init:

• run_init_exec_t — Set files with the run_init_exec_t type, if you want to transition an executable to the run_init_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. no cap, chcon alone is not the move 😤

---

🔥 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. yes, a whole GUI, for the girlies who like buttons 🖱️✨

---

🙈 AUTHOR 🙈

This manual page was auto-generated using sepolicy manpage. the sepolicy manpage tool ate and left no crumbs 🤖💖

---

🎀 SEE ALSO 🎀

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

---

k that's the whole page bestie, go be secure 💜 and hey — this one's signed run_init, dated 26-10-06, so if anyone asks, that's the source/version and date, mwah 🫶✨