syste...elinux(8)

📦

version 44.11 · 4 versions

✨ syste...elinux — the systemd_kdump_dep_generator SELinux manual ✨

okay bestie, pull up a chair 🫶 this is the syste...elinux(8) page, aka the SELinux policy lowdown for the systemd_kdump_dep_generator processes. it's giving security, it's giving mandatory access control, it's giving everything. let's get into it 💅

NAME 💖

systemd_kdump_dep_generator_selinux — Security Enhanced Linux Policy for the systemd_kdump_dep_generator processes

DESCRIPTION 🦋

Security-Enhanced Linux secures the systemd_kdump_dep_generator processes via flexible mandatory access control. no cap, that's the whole vibe.

The systemd_kdump_dep_generator processes execute with the systemd_kdump_dep_generator_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 systemd_kdump_dep_generator_t

ENTRYPOINTS 🚪

the systemd_kdump_dep_generator_t SELinux type can be entered via the systemd_kdump_dep_generator_exec_t file type. that's the doorway, periodt.

the default entrypoint paths for the systemd_kdump_dep_generator_t domain are literally these:

/usr/lib/systemd/system-generators/kdump-dep-generator.sh

PROCESS TYPES 👑

SELinux defines process types (domains) for each process running on the system. every process gets its own little identity, iconic behavior 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 systemd_kdump_dep_generator policy is very flexible allowing users to setup their systemd_kdump_dep_generator processes in as secure a method as possible.

the following process types are defined for systemd_kdump_dep_generator:

systemd_kdump_dep_generator_t

Note: semanage permissive -a systemd_kdump_dep_generator_t can be used to make the process type systemd_kdump_dep_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 but it's still watching 👀

BOOLEANS 🎀

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

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

MANAGED FILES 🗂️

the SELinux process type systemd_kdump_dep_generator_t can manage files labeled with the following file types. the paths listed are the default paths for these file types. heads up though — the processes UID still need to have DAC permissions. SELinux isn't doing your whole job for you, sorry babe 😭

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
root_t
- /sysroot/.aleph-version.json
- /sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
- /
- /initrd

FILE CONTEXTS 🌈

SELinux requires files to have an extended attribute to define the file type. it's like a little name tag but for files, obsessed.

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

STANDARD FILE CONTEXT 🧚

SELinux defines the file context types for the systemd_kdump_dep_generator, 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.

semanage fcontext -a -t systemd_kdump_dep_generator_exec_t '/srv/systemd_kdump_dep_generator/content(/.*)?'
restorecon -R -v /srv/mysystemd_kdump_dep_generator_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_kdump_dep_generator:

systemd_kdump_dep_generator_exec_t
- Set files with the systemd_kdump_dep_generator_exec_t type, if you want to transition an executable to the systemd_kdump_dep_generator_t domain.
systemd_kdump_dep_generator_unit_file_t
- Set files with the systemd_kdump_dep_generator_unit_file_t type, if you want to treat the files as systemd kdump dep generator 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. You will need to use restorecon to apply the labels. temporary vs permanent, know the difference bestie 💅

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.

AUTHOR 🌟

This manual page was auto-generated using sepolicy manpage.