DIRSRVADMIN_UNCONFINED_SCRIPT_SELINUX(8)
π¦ dirsrvadmin_unconfined_script_selinux(8) β the SELinux tea β
okay so bestie, welcome to the manual page for dirsrvadmin_unconfined_script_selinux, section 8 of the manual. she's a whole mood and she's about to explain, in excruciating but loving detail, how the dirsrvadmin_unconfined_script processes get locked down by Security-Enhanced Linux π
β¨ NAME β¨
dirsrvadmin_unconfined_script_selinux β the Security Enhanced Linux Policy for the dirsrvadmin_unconfined_script processes, periodt.
πΈ DESCRIPTION πΈ
Security-Enhanced Linux secures the dirsrvadmin_unconfined_script processes via flexible mandatory access control. literally the whole point π«Ά
The dirsrvadmin_unconfined_script processes execute with the dirsrvadmin_unconfined_script_t SELinux type. wanna vibe check whether you actually have these processes running? just run the ps command with the -Z qualifier. for example:
ps -eZ | grep dirsrvadmin_unconfined_script_t
that's it, that's the check π
πͺ ENTRYPOINTS πͺ
so the dirsrvadmin_unconfined_script_t SELinux type can be entered via the shell_exec_t and dirsrvadmin_unconfined_script_exec_t file types. two doors, both valid β¨
the default entrypoint paths for the dirsrvadmin_unconfined_script_t domain are, and I'm listing every single one because we don't skip:
/bin/d?ash, /bin/ksh.*, /bin/zsh.*, /usr/bin/d?ash, /usr/bin/ksh.*,
/usr/bin/zsh.*, /bin/esh, /bin/bash, /bin/fish, /bin/mksh, /bin/sash,
/bin/tcsh, /bin/yash, /bin/bash2, /usr/bin/esh, /sbin/nologin,
/usr/bin/bash, /usr/bin/fish, /usr/bin/mksh, /usr/bin/sash,
/usr/bin/tcsh, /usr/bin/yash, /usr/bin/bash2, /usr/sbin/sesh,
/usr/sbin/smrsh, /usr/bin/scponly, /usr/libexec/sesh, /usr/sbin/nologin,
/usr/bin/git-shell, /usr/sbin/scponlyc, /usr/libexec/sudo/sesh,
/usr/bin/cockpit-bridge, /usr/libexec/cockpit-agent, /usr/libexec/git-core/git-shell,
/usr/lib/dirsrv/cgi-bin/ds_create, /usr/lib/dirsrv/cgi-bin/ds_remove
like, yes, that's a lot of shells. no cap, they're all there π
π PROCESS TYPES π
SELinux defines process types (domains) for each process running on the system. iconic behaviour honestly.
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 dirsrvadmin_unconfined_script policy is very flexible, allowing users to setup their dirsrvadmin_unconfined_script processes in as secure a method as possible. slay π
the following process types are defined for dirsrvadmin_unconfined_script:
dirsrvadmin_unconfined_script_t
Note:semanage permissive -a dirsrvadmin_unconfined_script_tcan be used to make the process typedirsrvadmin_unconfined_script_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, she's chill but she still snitches π
π BOOLEANS π
SELinux policy is customizable based on least access required. the dirsrvadmin_unconfined_script policy is extremely flexible and has several booleans that allow you to manipulate the policy and run dirsrvadmin_unconfined_script with the tightest access possible. we love a configurable queen π
- if you want to deny user domains applications to map a memory region as both executable and writable β this is dangerous and the executable should be reported in bugzilla β you must turn on the
deny_execmemboolean. Disabled by default.
setsebool -P deny_execmem 1
- if you want to control the ability to mmap a low area of the address space, as configured by
/proc/sys/vm/mmap_min_addr, you must turn on themmap_low_allowedboolean. Disabled by default.
setsebool -P mmap_low_allowed 1
- if you want to disable kernel module loading, you must turn on the
secure_mode_insmodboolean. Disabled by default.
setsebool -P secure_mode_insmod 1
- if you want to allow unconfined executables to make their heap memory executable β doing this is a really bad idea, probably indicates a badly coded executable, but could indicate an attack, and this executable should be reported in bugzilla β you must turn on the
selinuxuser_execheapboolean. Disabled by default. π
setsebool -P selinuxuser_execheap 1
- if you want to allow unconfined executables to make their stack executable β this should never, ever be necessary, probably indicates a badly coded executable, but could indicate an attack, and this executable should be reported in bugzilla β you must turn on the
selinuxuser_execstackboolean. Enabled by default. π
setsebool -P selinuxuser_execstack 1
ποΈ MANAGED FILES ποΈ
the SELinux process type dirsrvadmin_unconfined_script_t can manage files labeled with the following file types. the paths listed are the default paths for these file types. quick reminder bestie: the processes UID still need to have DAC permissions. SELinux can't fix everything for you π«Ά
file_typeβ all files on the system
π·οΈ FILE CONTEXTS π·οΈ
SELinux requires files to have an extended attribute to define the file type. that's just how she rolls.
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 dirsrvadmin_unconfined_script policy is very flexible allowing users to setup their dirsrvadmin_unconfined_script processes in as secure a method as possible. (yes, we said that in PROCESS TYPES too, she's consistent π)
the following file types are defined for dirsrvadmin_unconfined_script:
dirsrvadmin_unconfined_script_exec_tβ set files with thedirsrvadmin_unconfined_script_exec_ttype if you want to transition an executable to thedirsrvadmin_unconfined_script_tdomain.
Paths:
/usr/lib/dirsrv/cgi-bin/ds_create, /usr/lib/dirsrv/cgi-bin/ds_remove
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, know the difference bestie π₯
π§° COMMANDS π§°
these tools are all your besties here:
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. GUI girlies, this one's for you π
π AUTHOR π
this manual page was auto-generated using sepolicy manpage. a bot wrote this and honestly? she ate π€β¨
β SEE ALSO β
selinux(8), dirsrvadmin_unconfined_script(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8) β go read those too, iykyk π
okay that's the whole page bestie, go forth and be secure π β¨
sign-off szn: this page is dirsrvadmin_unconfined_script (that's the source/version, mwah), dated 26-10-23, and it lives at dirsr...elinux(8) in the manual. love u, bye π¦π
π¦ where this page comes from
- centos-stream 9: selinux-policy-doc 38.1.87-1.el9 Β· GPLv2+
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms