systemd...selinux(8)
πΈ 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_tcan be used to make the process typesystemd_zram_generator_tpermissive. 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 thesystemd_zram_generator_conf_ttype if you want to treat the files as systemd zram generator configuration data, usually stored under the/etcdirectory.
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 thesystemd_zram_generator_exec_ttype if you want to transition an executable to thesystemd_zram_generator_tdomain. slay, a domain transition β¨systemd_zram_generator_unit_file_tβ set files with thesystemd_zram_generator_unit_file_ttype if you want to treat the files as systemd zram generator unit content.
Note: file context can be temporarily modified with thechconcommand. if you want to permanently change the file context you need to use thesemanage fcontextcommand β that modifies the SELinux labeling database. and you will need to userestoreconto apply the labels. temporary vs permanent, know the difference bestie π
π«Ά COMMANDS π«Ά
semanage fcontextcan also be used to manipulate default file context mappings.semanage permissivecan also be used to manipulate whether or not a process type is permissive.semanage modulecan also be used to enable/disable/install/remove policy modules.semanage booleancan also be used to manipulate the booleans.system-config-selinuxis 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
- opensuse-leap 16.0: selinux-policy-doc 20250627+git412.dbf877ab7-160000.1.1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms