syste...elinux(8)
β¨ syste...elinux(8) β the glow-up edition β¨
okay so bestie, lemme put you on to the syste...elinux(8) page π
this is the SELinux lowdown for systemd_ibft_rule_generator, and it's literally iconic. no cap.
π NAME π
systemd_ibft_rule_generator_selinux β Security Enhanced Linux Policy for the systemd_ibft_rule_generator processes. it's giving "protect the generator" energy fr fr π‘οΈβ¨
πΈ DESCRIPTION πΈ
Security-Enhanced Linux secures the systemd_ibft_rule_generator processes via flexible mandatory access control. yes bestie, that's the whole vibe β mandatory access control, not optional, not vibes-based. periodt π₯
The systemd_ibft_rule_generator processes execute with the systemd_ibft_rule_generator_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier.
For example β run this and see what shows up π:
ps -eZ | grep systemd_ibft_rule_generator_t
π¦ ENTRYPOINTS π¦
The systemd_ibft_rule_generator_t SELinux type can be entered via the systemd_ibft_rule_generator_exec_t file type. that's the doorway, the portal, the main character entrance πͺβ¨
The default entrypoint paths for the systemd_ibft_rule_generator_t domain are the following:
/usr/lib/systemd/system-generators/ibft-rule-generator
π PROCESS TYPES π
SELinux defines process types (domains) for each process running on the system. each process gets its own little domain era, we love to see it π
You can see the context of a process using the -Z option to ps. iconic flag, truly.
Policy governs the access confined processes have to files. SELinux systemd_ibft_rule_generator policy is very flexible allowing users to setup their systemd_ibft_rule_generator processes in as secure a method as possible. flexible AND secure? she contains multitudes π
The following process types are defined for systemd_ibft_rule_generator:
systemd_ibft_rule_generator_t
Note:semanage permissive -a systemd_ibft_rule_generator_tcan be used to make the process typesystemd_ibft_rule_generator_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so likeβ¦ she won't block you, but she WILL be taking notes ππ
π₯ BOOLEANS π₯
SELinux policy is customizable based on least access required. systemd_ibft_rule_generator policy is extremely flexible and has several booleans that allow you to manipulate the policy and run systemd_ibft_rule_generator with the tightest access possible. tightest access possible β that's the aesthetic π
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_ibft_rule_generator_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. okay so DAC perms still matter, don't forget the basics bestie π«Ά
π§ 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. every file needs its label, no label no entry, iykyk π·οΈ
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_ibft_rule_generator policy is very flexible allowing users to setup their systemd_ibft_rule_generator processes in as secure a method as possible.
β STANDARD FILE CONTEXT β
SELinux defines the file context types for the systemd_ibft_rule_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_ibft_rule_generator_exec_t '/srv/systemd_ibft_rule_generator/content(/.*)?'
restorecon -R -v /srv/mysystemd_ibft_rule_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_ibft_rule_generator:
π systemd_ibft_rule_generator_exec_t
- Set files with the
systemd_ibft_rule_generator_exec_ttype, if you want to transition an executable to thesystemd_ibft_rule_generator_tdomain.
π systemd_ibft_rule_generator_unit_file_t
- Set files with the
systemd_ibft_rule_generator_unit_file_ttype, if you want to treat the files as systemd ibft rule 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. This will modify the SELinux labeling database. You will need to userestoreconto apply the labels. temporary vs permanent, choose wisely bestie βchconis the fleeting vibe,semanage fcontextis forever π
π 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.
π«Ά AUTHOR π«Ά
This manual page was auto-generated using sepolicy manpage. auto-generated and still ate π
β¨
π SEE ALSO π
selinux(8), systemd_ibft_rule_generator(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8)
the whole squad is here, go read them too, you're welcome π«Άπ
and that's the tea, bestie β β this page is from the syste...elinux(8) manual, dated 26-10-06. go forth and SELinux responsibly πβ¨π
π¦ 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