coreos...elinux(8)

💅 coreos_installer_generator_selinux — SELinux Policy, but make it a group chat

okay so bestie, this page lives in the SELinux Policy manual section for coreos_installer_generator — and no cap, it's the whole glow-up guide for how SELinux keeps those processes in check. grab a strawberry drink 🍓 and let's go.

---

✨ NAME ✨

coreos_installer_generator_selinux — Security Enhanced Linux Policy for the coreos_installer_generator processes 🎀

---

🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the coreos_installer_generator processes via flexible mandatory access control. literally the whole vibe: SELinux is the bouncer, and it's checking IDs at the door 💅

The coreos_installer_generator processes execute with the coreos_installer_generator_t SELinux type. wanna check if you've got these processes running? just run the ps command with the -Z qualifier. slay, easy.

for example:

ps -eZ | grep coreos_installer_generator_t

---

🦋 ENTRYPOINTS 🦋

The coreos_installer_generator_t SELinux type can be entered via the coreos_installer_generator_exec_t file type. that's the doorway, bestie 🚪✨

the default entrypoint paths for the coreos_installer_generator_t domain are literally just:

/usr/lib/systemd/system-generators/coreos-installer-generator

---

👑 PROCESS TYPES 👑

SELinux defines process types (domains) for each process running on the system. everyone gets a label, no exceptions 💖

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 coreos_installer_generator policy is very flexible, allowing users to setup their coreos_installer_generator processes in as secure a method as possible. iconic behaviour honestly.

the following process types are defined for coreos_installer_generator:

• coreos_installer_generator_t

Note: semanage permissive -a coreos_installer_generator_t can be used to make the process type coreos_installer_generator_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, it stops blocking you but it will still be in the group chat taking receipts 📸

---

🎀 BOOLEANS 🎀

SELinux policy is customizable based on least access required. the coreos_installer_generator policy is extremely flexible and has several booleans that allow you to manipulate the policy and run coreos_installer_generator with the tightest access possible. tightest access = cleanest fit, periodt.

If you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean. Enabled by default, bestie — it already ate 💅

setsebool -P fips_mode 1

---

💜 MANAGED FILES 💜

The SELinux process type coreos_installer_generator_t can manage files labeled with the following file types. the paths listed are the default paths for these file types. note: the process's UID still needs to have DAC permissions (SELinux isn't doing all the work, okay?? 😭).

mdadm_conf_t

/etc/mdadm.conf.d(/.*)?
/etc/mdadm.conf
/etc/mdadm.conf.anacbak

---

🌈 FILE CONTEXTS 🌈

SELinux requires files to have an extended attribute to define the file type. it's giving ✨labels on everything✨.

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 coreos_installer_generator policy is very flexible, allowing users to setup their coreos_installer_generator processes in as secure a method as possible. yes we said that already. it's still true. 🫶

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for the coreos_installer_generator. if you wanted to store files with these types in a different paths (yes, that grammar is the manpage's, not mine, love her anyway 💀), 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 coreos_installer_generator_exec_t '/srv/coreos_installer_generator/content(/.*)?'
restorecon -R -v /srv/mycoreos_installer_generator_content

Note: SELinux often uses regular expressions to specify labels that match multiple files. regex is her love language, iykyk 🔥

the following file types are defined for coreos_installer_generator:

coreos_installer_generator_exec_t

• Set files with the coreos_installer_generator_exec_t type, if you want to transition an executable to the coreos_installer_generator_t domain. gateway executable behaviour 💫

coreos_installer_generator_unit_file_t

• Set files with the coreos_installer_generator_unit_file_t type, if you want to treat the files as coreos installer generator unit content. so iconic of them.

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 = cute for now, permanent = semanage + restorecon, no shortcuts 🙈

---

🔥 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. a whole GUI, for the girls who don't do terminal-only 💅

---

🌺 AUTHOR 🌺

This manual page was auto-generated using sepolicy manpage. not me being a bot-written baddie 😭

---

🧚 SEE ALSO 🧚

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

---

and that's the page, bestie 💖 this was coreos_installer_generator from the SELinux policy set, dated 26-10-06, signed off in coreos...elinux(8) energy. now go label something. slay 🎀✨