olak_selinux(8)
π olak_selinux β the manual, but make it make sense π
okay bestie, gather round, because this is the olak_selinux(8) page β that's section 8 of the manual, the SELinux Policy one for olak. yes it's a whole policy page. yes it's a lot. no we are NOT skipping anything. let's go π«Ά
β¨ NAME β¨
olak_selinux β the Security Enhanced Linux Policy for the olak processes. that's the whole name. iconic, concise, we love her π
πΈ DESCRIPTION πΈ
so, Security-Enhanced Linux secures the olak processes via flexible mandatory access control. that's the vibe. that's literally the whole point. π₯
the olak processes execute with the olak_t SELinux type. you wanna check if you've got these processes running? run the ps command with the -Z qualifier, babe.
for example:
ps -eZ | grep olak_t
that's it. that's the check. go off π
π¦ ENTRYPOINTS π¦
the olak_t SELinux type can be entered via the olak_exec_t file type. that's the doorway, the portal, the little gateway πͺβ¨
the default entrypoint paths for the olak_t domain are the following:
/usr/bin/openssh-ldap-authkeys
one path. one single path. she's lowkey exclusive π
π PROCESS TYPES π
SELinux defines process types (domains) for each process running on the system. so every process gets a lil identity, a lil domain, a lil main character energy β¨
you can see the context of a process using the -Z option to ps. same trick as before, it just keeps working π
Policy governs the access confined processes have to files. SELinux olak policy is very flexible, allowing users to setup their olak processes in as secure a method as possible. flexible AND secure?? she does both, no cap π«Ά
the following process types are defined for olak:
olak_t
Note:semanage permissive -a olak_tcan be used to make the process typeolak_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated.
so like β permissive means it won't block you, but it WILL still snitch in the AVC messages. it's giving "i'm not mad i'm just disappointed" π
π BOOLEANS π
SELinux policy is customizable based on least access required. olak policy is extremely flexible and has several booleans that allow you to manipulate the policy and run olak with the tightest access possible. tightest access = tightest fit = slay π₯
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
that -P keeps it persistent across reboots, bestie. do not forget the -P unless you want to do this again π
π§ MANAGED FILES π§
the SELinux process type olak_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 is not out here overriding your normal Unix permissions, okay? both systems have to say yes. it's a two-yes situation π
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/var/run/crm(/.*)?/var/run/cman_.*/var/run/rsctmp(/.*)?/var/run/aisexec.*/var/run/heartbeat(/.*)?/var/run/pcsd-ruby.socket/var/run/corosync-qnetd(/.*)?/var/run/corosync-qdevice(/.*)?/var/run/corosync.pid/var/run/cpglockd.pid/var/run/rgmanager.pid/var/run/cluster/rgmanager.sk
root_t/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?//initrd
var_run_t/run/.*/var/run/.*/run/var/run/var/run/var/spool/postfix/pid
(yes, /var/run appears twice in that list. i'm not editing the source, that's just what she says, and honestly? iconic. periodt π
)
π FILE CONTEXTS π
SELinux requires files to have an extended attribute to define the file type. no extended attribute, no vibes. that's the rule π
you can see the context of a file using the -Z option to ls. third time we've used -Z on something and honestly? consistency queen π
Policy governs the access confined processes have to these files. SELinux olak policy is very flexible, allowing users to setup their olak processes in as secure a method as possible.
the following file types are defined for olak:
olak_exec_tβ set files with theolak_exec_ttype, if you want to transition an executable to theolak_tdomain.
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.
so like: chcon = temporary glow-up, semanage fcontext = permanent record, restorecon = actually putting it on. all three, or it doesn't count π«Ά
β 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 booleanssystem-config-selinuxis a GUI tool available to customize SELinux policy settings.
GUI tool mentioned in a manpage?? we love a little visual moment β¨
π AUTHOR π
This manual page was auto-generated using sepolicy manpage. yes bestie, a robot wrote this. and she ate. π€π
π SEE ALSO π
selinux(8), olak(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8)
okay that's the whole page, nothing skipped, nothing faked, every path and every boolean exactly where it belongs π
this lil gem is olak from 23-02-19, shipped as part of the olak_selinux(8) manual. go forth, run ps -eZ | grep olak_t, and be the most secure olak_t you can be πΈπ¦π
π¦ where this page comes from
- epel 9: openssh-ldap-authkeys-selinux 0.2.0^git20230224.62ece4b-1.el9 Β· MIT
- fedora 43: openssh-ldap-authkeys-selinux 0.2.0^git20230224.62ece4b-12.fc43 Β· MIT
- fedora 44: openssh-ldap-authkeys-selinux 0.2.0^git20230224.62ece4b-13.fc44 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms