dirsrv_selinux(8)

📦
version 20250627+git412.dbf877ab7 · 7 versions
, in opensuse-leap 16.0

💖 dirsrv_selinux(8) — the SELinux Policy for dirsrv, explained 🎀

okay bestie, so this is the manual page for dirsrv_selinux — literally the whole SELinux policy situation for the dirsrv processes. it's giving "niche but iconic" and we're gonna get through it together, no cap 💅

✨ NAME ✨

dirsrv_selinux — the Security Enhanced Linux Policy for the dirsrv processes. periodt.

🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the dirsrv processes via flexible mandatory access control. yes, mandatory — SELinux does not ask nicely, she just is the rule ✨

The dirsrv processes execute with the dirsrv_t SELinux type. you can check if you have these processes running by executing the ps command with the -Z qualifier, like so:

ps -eZ | grep dirsrv_t

run it, it's a vibe check for your processes fr fr 🦋

🎀 ENTRYPOINTS 🎀

The dirsrv_t SELinux type can be entered via the dirsrv_exec_t file type.

the default entrypoint paths for the dirsrv_t domain are literally just:

/usr/bin/ns-slapd

that's the one door in, bestie 🚪✨

💜 PROCESS TYPES 💜

SELinux defines process types (domains) for each process running on the system. so every process gets its own little domain, main character energy for everyone 👑

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 dirsrv policy is very flexible, allowing users to setup their dirsrv processes in as secure a method as possible. flexible and secure, we love a multitasker 💅

the following process types are defined for dirsrv:

  • dirsrv_t
  • dirsrv_snmp_t
Note: semanage permissive -a dirsrv_t can be used to make the process type dirsrv_t permissive. 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. the dirsrv policy is extremely flexible and has several booleans that allow you to manipulate the policy and run dirsrv with the tightest access possible. tightest access = cleanest look, obviously ✨

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 confined applications to run with kerberos, you must turn on the kerberos_enabled boolean. enabled by default.

setsebool -P kerberos_enabled 1

if you want to allow system to run with NIS, you must turn on the nis_enabled boolean. disabled by default — so flip it yourself if that's your journey 🫶

setsebool -P nis_enabled 1

🦋 MANAGED FILES 🦋

The SELinux process type dirsrv_t can manage files labeled with the following file types. the paths listed are the default paths for these file types. and hiii quick reminder: note the processes UID still need to have DAC permissions. SELinux is not out here overriding DAC, she's just extra on top 💀

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

dirsrv_config_t

/etc/dirsrv(/.*)?

dirsrv_tmp_t

dirsrv_tmpfs_t

/dev/shm/slapd-.*

dirsrv_var_lib_t

/var/lib/dirsrv(/.*)?

dirsrv_var_lock_t

/run/lock/dirsrv(/.*)?

dirsrv_var_log_t

/var/log/dirsrv(/.*)?

dirsrv_var_run_t

/run/slapd.*
/run/dirsrv(/.*)?

faillog_t

/var/log/btmp.*
/run/faillock(/.*)?
/var/log/faillog.*
/var/log/tallylog.*

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

lastlog_t

/var/log/lastlog.*
/var/lib/lastlog(/.*)?

root_t

/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
/var/lib/ntp

security_t

/selinux

systemd_passwd_var_run_t

/run/systemd/ask-password(/.*)?
/run/systemd/ask-password-block(/.*)?

wtmpdb_journal_t

/var/lib/wtmpdb/wtmp.db-journal

like okay that's a LOT of paths but bestie we do not skip a single one, every path ate and left no crumbs 💅✨

🔥 FILE CONTEXTS 🔥

SELinux requires files to have an extended attribute to define the file type.

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 dirsrv policy is very flexible, allowing users to setup their dirsrv processes in as secure a method as possible. yes she said it again, because it's important 😌

⭐ EQUIVALENCE DIRECTORIES ⭐

dirsrv policy stores data with multiple different file context types under the /var/log/dirsrv directory. if you would like to store the data in a different directory you can use the semanage command to create an equivalence mapping. if you wanted to store this data under the /srv directory you would execute the following command:

semanage fcontext -a -e /var/log/dirsrv /srv/dirsrv
restorecon -R -v /srv/dirsrv

mapping made, labels applied, slay ✅

💫 STANDARD FILE CONTEXT 💫

SELinux defines the file context types for the dirsrv, 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. it's a two-step, don't skip step two 🙈

semanage fcontext -a -t dirsrv_exec_t '/srv/dirsrv/content(/.*)?'
restorecon -R -v /srv/mydirsrv_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. cute regex moment 🎀

the following file types are defined for dirsrv:

dirsrv_config_t

  • set files with the dirsrv_config_t type, if you want to treat the files as dirsrv configuration data, usually stored under the /etc directory.

dirsrv_exec_t

  • set files with the dirsrv_exec_t type, if you want to transition an executable to the dirsrv_t domain.

dirsrv_share_t

  • set files with the dirsrv_share_t type, if you want to treat the files as dirsrv share data.

dirsrv_snmp_exec_t

  • set files with the dirsrv_snmp_exec_t type, if you want to transition an executable to the dirsrv_snmp_t domain.

Paths:

/usr/bin/ldap-agent, /usr/bin/ldap-agent-bin

dirsrv_snmp_var_log_t

  • set files with the dirsrv_snmp_var_log_t type, if you want to treat the data as dirsrv snmp var log data, usually stored under the /var/log directory.

dirsrv_snmp_var_run_t

  • set files with the dirsrv_snmp_var_run_t type, if you want to store the dirsrv snmp files under the /run or /var/run directory.

dirsrv_tmp_t

  • set files with the dirsrv_tmp_t type, if you want to store dirsrv temporary files in the /tmp directories.

dirsrv_tmpfs_t

  • set files with the dirsrv_tmpfs_t type, if you want to store dirsrv files on a tmpfs file system.

dirsrv_unit_file_t

  • set files with the dirsrv_unit_file_t type, if you want to treat the files as dirsrv unit content.

dirsrv_var_lib_t

  • set files with the dirsrv_var_lib_t type, if you want to store the dirsrv files under the /var/lib directory.

dirsrv_var_lock_t

  • set files with the dirsrv_var_lock_t type, if you want to treat the files as dirsrv var lock data, stored under the /var/lock directory

dirsrv_var_log_t

  • set files with the dirsrv_var_log_t type, if you want to treat the data as dirsrv var log data, usually stored under the /var/log directory.

dirsrv_var_run_t

  • set files with the dirsrv_var_run_t type, if you want to store the dirsrv files under the /run or /var/run directory.

Paths:

/run/slapd.*, /run/dirsrv(/.*)?
Note: file context can be temporarily modified with the chcon command. If you want to permanently change the file context you need to use the semanage fcontext command. This will modify the SELinux labeling database. You will need to use restorecon to apply the labels. temporary vs permanent, know the difference bestie 😭✨

👑 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 the girlies who like a little visual moment 🖱️💖

🌸 AUTHOR 🌸

This manual page was auto-generated using sepolicy manpage . — yes the robot wrote it, and we thank her for her service 🫶

💜 SEE ALSO 💜

(yes dirsrv_snmp_selinux(8) is listed twice — she said it twice because she meant it twice, and we keep it exactly as-is 💅✨)

aaaand that's the whole page bestie, you ate that reading era up 🔥 this cutie was brought to you by dirsrv, version/date 26-10-06, filed under dirsrv_selinux(8) — mwah, go forth and confine your processes responsibly 🎀💖

📦 where this page comes from