systemd...selinux(8)

πŸ“¦
version 20250627+git412.dbf877ab7 Β· 6 versions
, in opensuse-leap 16.0

🌸 systemd...selinux(8) 🌸

okay bestie so this is the manual page for systemd...selinux(8) β€” the SELinux policy page, and today's main character is the systemd_zram_generator policy. yes that's a whole lot of underscores, we're gonna get through it together πŸ’…


✨ NAME ✨

systemd_zram_generator_selinux β€” the Security Enhanced Linux Policy for the systemd_zram_generator processes 🫢


πŸ’– DESCRIPTION πŸ’–

Security-Enhanced Linux keeps the systemd_zram_generator processes safe and sound via flexible mandatory access control. that's the whole vibe β€” mandatory access control, no cap πŸ”₯

so here's the thing: the systemd_zram_generator processes run with the systemd_zram_generator_t SELinux type. and you can literally check if you've got these processes running by running the ps command with the -Z qualifier. easy.

for example:

ps -eZ | grep systemd_zram_generator_t

πŸ¦‹ ENTRYPOINTS πŸ¦‹

you can enter the systemd_zram_generator_t SELinux type via the systemd_zram_generator_exec_t file type. that's the door, that's the gateway, that's the entrypoint ✨

the default entrypoint paths for the systemd_zram_generator_t domain are the following:

/usr/lib/systemd/system-generators/zram-generator

πŸ‘‘ PROCESS TYPES πŸ‘‘

so SELinux defines process types (aka domains) for each process running on the system πŸ’œ

you can see the context of a process using the -Z option to ps β€” iconic, honestly.

policy governs the access that confined processes have to files. the SELinux systemd_zram_generator policy is very flexible, allowing users to set up their systemd_zram_generator processes in as secure a method as possible. main character security energy.

the following process types are defined for systemd_zram_generator:

  • systemd_zram_generator_t
Note: semanage permissive -a systemd_zram_generator_t can be used to make the process type systemd_zram_generator_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, you're not off the hook, the receipts still exist πŸ™ˆ

🌈 BOOLEANS 🌈

SELinux policy is customizable based on least access required. and the systemd_zram_generator policy is extremely flexible and has several booleans that let you manipulate the policy and run systemd_zram_generator with the tightest access possible. love that for us πŸŽ€

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_zram_generator_t can manage files labeled with the following file types. the paths listed are the default paths for these file types. and heads up β€” the process's UID still needs to have DAC permissions, no skipping that part ⭐

  • 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

πŸ“ FILE CONTEXTS πŸ“

SELinux requires files to have an extended attribute to define the file type. that's just how it is, bestie πŸ’…

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

🌸 STANDARD FILE CONTEXT 🌸

SELinux defines the file context types for the systemd_zram_generator. so 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. iconic two-step πŸŽ€

semanage fcontext -a -t systemd_zram_generator_exec_t '/srv/systemd_zram_generator/content(/.*)?'
restorecon -R -v /srv/mysystemd_zram_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_zram_generator:

  • systemd_zram_generator_conf_t β€” set files with the systemd_zram_generator_conf_t type if you want to treat the files as systemd zram generator configuration data, usually stored under the /etc directory.

Paths:

/etc/systemd/zram-generator.conf
/run/systemd/zram-generator.conf
/usr/lib/systemd/zram-generator.conf
  • systemd_zram_generator_exec_t β€” set files with the systemd_zram_generator_exec_t type if you want to transition an executable to the systemd_zram_generator_t domain. slay, a domain transition ✨
  • systemd_zram_generator_unit_file_t β€” set files with the systemd_zram_generator_unit_file_t type if you want to treat the files as systemd zram 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 β€” that modifies the SELinux labeling database. and 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. yes, a GUI, for when the terminal is doing too much πŸ–₯️

⭐ AUTHOR ⭐

this manual page was auto-generated using sepolicy manpage. the robots wrote it, not me πŸ€–πŸ’–


πŸ’œ SEE ALSO πŸ’œ

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


and that's the whole page bestie, you ate that πŸŽ€ mwah πŸ’‹

little sign-off for the receipts: this was systemd_zram_generator, dated 26-10-06, from the systemd...selinux(8) manual. periodt. 🌈

πŸ“¦ where this page comes from