coreos_i..._selinux(8)

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

💅 coreos_i..._selinux(8) — the coreos_installer_selinux glow-up

okay so you opened the coreos_i..._selinux(8) man page and it's giving "SELinux policy for coreos_installer" — that's literally the vibe, bestie. Buckle up, we're doing this together 💖

✨ NAME ✨

coreos_installer_selinux — Security Enhanced Linux Policy for the coreos_installer processes 🫶

🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the coreos_installer processes via flexible mandatory access control. That's the whole assignment. MAC rights, no cap 🔥

The coreos_installer processes execute with the coreos_installer_t SELinux type. Wanna check if you've got these processes running? Just run the ps command with the -Z qualifier. Easy.

For example:

ps -eZ | grep coreos_installer_t

🦋 ENTRYPOINTS 🦋

The coreos_installer_t SELinux type can be entered via the coreos_installer_exec_t file type. That's the door, okay? 👑

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

/usr/bin/coreos-installer, /usr/libexec/coreos-installer-service,
/usr/libexec/coreos-installer-disable-device-auto-activation

👑 PROCESS TYPES 👑

SELinux defines process types (domains) for each process running on the system. Every process gets a lil identity, iconic honestly.

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

Policy governs the access confined processes have to files. SELinux coreos_installer policy is very flexible, allowing users to setup their coreos_installer processes in as secure a method as possible ✨

The following process types are defined for coreos_installer:

coreos_installer_t, coreos_installer_generator_t
Note: semanage permissive -a coreos_installer_t can be used to make the process type coreos_installer_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 absolutely still tells on you 💀

🎀 BOOLEANS 🎀

SELinux policy is customizable based on least access required. The coreos_installer policy is extremely flexible and has several booleans that allow you to manipulate the policy and run coreos_installer with the tightest access possible. Tightest access = main character energy 👑

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 confined applications to use nscd shared memory, you must turn on the nscd_use_shm boolean. Enabled by default.

setsebool -P nscd_use_shm 1

🧚 MANAGED FILES 🧚

The SELinux process type coreos_installer_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 out here doing DAC's homework for it, periodt.

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

coreos_installer_var_run_t

/run/ostree-live
/run/coreos-installer-reboot

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. xattrs are literally the moment, ngl.

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

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for the coreos_installer. 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-step process, both slay.

semanage fcontext -a -t coreos_installer_exec_t '/srv/coreos_installer/content(/.*)?'
restorecon -R -v /srv/mycoreos_installer_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 coreos_installer:

coreos_installer_exec_t

  • Set files with the coreos_installer_exec_t type, if you want to transition an executable to the coreos_installer_t domain.

Paths:

/usr/bin/coreos-installer, /usr/libexec/coreos-installer-service,
/usr/libexec/coreos-installer-disable-device-auto-activation

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.

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.

coreos_installer_unit_file_t

  • Set files with the coreos_installer_unit_file_t type, if you want to treat the files as coreos installer unit content.

coreos_installer_var_run_t

  • Set files with the coreos_installer_var_run_t type, if you want to store the coreos installer files under the /run or /var/run directory.

Paths:

/run/ostree-live, /run/coreos-installer-reboot
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. So chcon is the temporary tattoo and semanage fcontext + restorecon is the real ink, iykyk 💀

🔥 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 GUI!! For when you want to click instead of type 🖱️✨

🍓 AUTHOR 🍓

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

🌟 SEE ALSO 🌟

selinux(8), coreos_installer(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8), coreos_installer_generator_selinux(8), coreos_installer_generator_selinux(8)

(and yes, coreos_installer_generator_selinux(8) is listed twice in the original — she said it once for each of us 🫶)

okay that's the whole page, you ate that 💅 this one's coreos_installer, dated 26-10-06 — go forth and label things correctly, bestie 🌈💖

📦 where this page comes from