syste...linux(8)

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

💅 syste...linux(8) — the SELinux policy page for systemd_udev_trigger_generator, but make it make sense

okay bestie, grab a strawberry drink 🍓 because we're diving into the SELinux manual for the systemd_udev_trigger_generator processes. Yes, the manual name up top is literally syste...linux(8) (it's fancy and truncated, iykyk), and yes we're doing the whole thing. no skipping. let's go ✨

💖 NAME 💖

systemd_udev_trigger_generator_selinux — the Security Enhanced Linux Policy for the systemd_udev_trigger_generator processes. that's the whole name, she's long but she's iconic 👑

🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the systemd_udev_trigger_generator processes via flexible mandatory access control. that's the whole vibe — MAC, not the makeup kind, the mandatory access control kind 💅

The systemd_udev_trigger_generator processes execute with the systemd_udev_trigger_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_udev_trigger_generator_t

look at you go, checking contexts like a main character 🫶

🦋 ENTRYPOINTS 🦋

The systemd_udev_trigger_generator_t SELinux type can be entered via the systemd_udev_trigger_generator_exec_t file type. that's the door, that's the way in 🚪

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

/usr/lib/systemd/system-generators/udev-trigger-generator

one path. one legend. ⭐

👑 PROCESS TYPES 👑

SELinux defines process types (domains) for each process running on the system. yes, every single one gets a little domain 💜

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_udev_trigger_generator policy is very flexible, allowing users to setup their systemd_udev_trigger_generator processes in as secure a method as possible. flexible and secure, we love a duality ✨

The following process types are defined for systemd_udev_trigger_generator:

  • systemd_udev_trigger_generator_t
Note: semanage permissive -a systemd_udev_trigger_generator_t can be used to make the process type systemd_udev_trigger_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 still talks about you 😭 the receipts keep coming.

🎀 BOOLEANS 🎀

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

  • 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

two booleans, both already on, both slaying 🌈

🧚 MANAGED FILES 🧚

The SELinux process type systemd_udev_trigger_generator_t can manage files labeled with the following file types. the paths listed are the default paths for these file types. quick heads up though: the process's UID still needs to have DAC permissions. SELinux said yes, but your UID might still say no 🙈

  • 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
/var/lib/ntp

that's a lot of paths and every single one of them matters, no cap 🔥

🌟 FILE CONTEXTS 🌟

SELinux requires files to have an extended attribute to define the file type. it's giving "everything needs a label" energy 🏷️

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_udev_trigger_generator policy is very flexible, allowing users to setup their systemd_udev_trigger_generator processes in as secure a method as possible. yes, this sentence is basically the same as before, she's consistent and we respect it 💖

🌸 STANDARD FILE CONTEXT 🌸

SELinux defines the file context types for the systemd_udev_trigger_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. relocate, relabel, restore — the holy trinity ✨

semanage fcontext -a -t systemd_udev_trigger_generator_exec_t '/srv/systemd_udev_trigger_generator/content(/.*)?'
restorecon -R -v /srv/mysystemd_udev_trigger_generator_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regexes, in my labeling database? it's more likely than you think 🦋

The following file types are defined for systemd_udev_trigger_generator:

  • systemd_udev_trigger_generator_exec_t — set files with the systemd_udev_trigger_generator_exec_t type, if you want to transition an executable to the systemd_udev_trigger_generator_t domain.
  • systemd_udev_trigger_generator_unit_file_t — set files with the systemd_udev_trigger_generator_unit_file_t type, if you want to treat the files as systemd udev trigger 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 — one is a fling, one is a whole committed relationship 💀

⭐ 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 visual learners 🎀

🫶 AUTHOR 🫶

This manual page was auto-generated using sepolicy manpage. the robot wrote it, we just made it cute 🤖💅

🔥 SEE ALSO 🔥

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

go read those too, bestie, the lore goes deep 📚

aaaand that's the whole page! ✨ sign-off time: this gorgeous thing is systemd_udev_trigger_generator, date 26-10-06, living in the syste...linux(8) manual — go forth and label responsibly, ilysm 🧚💜

📦 where this page comes from