cgred_selinux(8)
π cgred_selinux(8) β the SELinux policy page for cgred, bestie edition π
okay so this is the manual for cgred_selinux, living in section 8 of the manual (the SELinux Policy cgred one, iykyk). it's giving "security paperwork but make it cute" and honestly? we're gonna get through it together π«Ά
β¨ NAME β¨
cgred_selinux β the Security Enhanced Linux Policy for the cgred processes π
πΈ DESCRIPTION πΈ
Security-Enhanced Linux secures the cgred processes via flexible mandatory access control. that's the whole vibe: SELinux is the bouncer, cgred is the guest, and the guest list is mandatory, no plus-ones π
The cgred processes execute with the cgred_t SELinux type. so if you're like "are my cgred processes even running rn" β you can check by executing the ps command with the -Z qualifier. literally that simple, no cap.
For example:
ps -eZ | grep cgred_t
run it. screenshot it. send it to the group chat πΈ
π¦ ENTRYPOINTS π¦
The cgred_t SELinux type can be entered via the cgred_exec_t file type. that's the doorway, bestie πͺβ¨
The default entrypoint paths for the cgred_t domain are the following:
/usr/bin/cgrulesengd
one single path. main character energy, honestly π
π PROCESS TYPES π
SELinux defines process types (domains) for each process running on the system. yes, each one. it's a whole roster π
You can see the context of a process using the -Z option to ps.
Policy governs the access confined processes have to files. the SELinux cgred policy is very flexible, allowing users to setup their cgred processes in as secure a method as possible. flexible and secure, we love a multitasker π
The following process types are defined for cgred:
cgred_t
Note:semanage permissive -a cgred_tcan be used to make the process typecgred_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like... it stops saying no, but it still writes down that it wanted to say no π the receipts stay, fr fr.
π BOOLEANS π
SELinux policy is customizable based on least access required. the cgred policy is extremely flexible and has several booleans that allow you to manipulate the policy and run cgred with the tightest access possible. booleans are basically lil on/off switches for policy behaviour and we are obsessed ποΈβ¨
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
If you want to allow system to run with NIS, you must turn on the nis_enabled boolean. Disabled by default.
setsebool -P nis_enabled 1
see how two of them are already enabled and one is chillin at disabled? that's not a typo, that's the actual defaults, don't come for me π
π MANAGED FILES π
The SELinux process type cgred_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. SELinux said "you may" but DAC said "do you have the credentials tho" β both checks, every time π
cgred_var_run_t
/run/cgred.*
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
krb5_host_rcache_t
/var/tmp/krb5_0.rcache2
/var/cache/krb5rcache(/.*)?
/var/tmp/nfs_0
/var/tmp/DNS_25
/var/tmp/host_0
/var/tmp/imap_0
/var/tmp/HTTP_23
/var/tmp/HTTP_48
/var/tmp/ldap_55
/var/tmp/ldap_487
/var/tmp/ldapmap1_0
root_t
/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
/var/lib/ntp
like, yes, / is in there. the root of everything. casual π
π§ FILE CONTEXTS π§
SELinux requires files to have an extended attribute to define the file type. it's not a vibe, it's a label π·οΈ
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 cgred policy is very flexible, allowing users to setup their cgred processes in as secure a method as possible. (yes, same sentence as before β the policy is flexible in both directions, she contains multitudes β¨)
β STANDARD FILE CONTEXT β
SELinux defines the file context types for the cgred. so 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. two steps, bestie, don't skip the second one π«Ά
semanage fcontext -a -t cgred_exec_t '/srv/cgred/content(/.*)?'
restorecon -R -v /srv/mycgred_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies rise πΈ
The following file types are defined for cgred:
cgred_exec_t
- Set files with the
cgred_exec_ttype, if you want to transition an executable to thecgred_tdomain. πͺ
cgred_initrc_exec_t
- Set files with the
cgred_initrc_exec_ttype, if you want to transition an executable to thecgred_initrc_tdomain.
cgred_log_t
- Set files with the
cgred_log_ttype, if you want to treat the data ascgredlog data, usually stored under the/var/logdirectory. π
cgred_var_run_t
- Set files with the
cgred_var_run_ttype, if you want to store thecgredfiles under the/runor/var/rundirectory.
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. tl;dr:chconis a temporary tattoo,semanage fcontext+restoreconis the real ink π periodt.
π 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 GUI! for when the terminal is doing too much π±οΈβ¨
π AUTHOR π
This manual page was auto-generated using sepolicy manpage. a robot wrote this and honestly it ate π€π
π SEE ALSO π
selinux(8), cgred(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8)
go read those next, iykyk ππ¦
and that's the whole page, bestie!! sign-off time: this one's from the cgred manual, dated 26-10-06, and it goes out to cgred_selinux(8). mwah ππβ¨
π¦ 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