dictd_selinux(8)

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

💅 dictd_selinux(8) — the SELinux policy page for dictd, bestie edition 🎀

okay so this is dictd_selinux(8), the manual page from the SELinux Policy dictd corner of the universe, and I'm gonna walk you through it like we're texting at 2am. grab a snack 🍓

✨ NAME ✨

dictd_selinux — Security Enhanced Linux Policy for the dictd processes. that's it, that's the whole vibe check 👑

🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the dictd processes via flexible mandatory access control. yes bestie, mandatory. it's not a suggestion, it's the law 💅

The dictd processes execute with the dictd_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier.

For example:

ps -eZ | grep dictd_t

literally just run it, it's giving "who dis" but for processes 🕵️‍♀️

🦋 ENTRYPOINTS 🦋

The dictd_t SELinux type can be entered via the dictd_exec_t file type.

The default entrypoint paths for the dictd_t domain are the following:

/usr/bin/dictd

one path. one icon. main character energy fr fr ✨

👑 PROCESS TYPES 👑

SELinux defines process types (domains) for each process running on the system

You can see the context of a process using the -Z option to ps

Policy governs the access confined processes have to files. SELinux dictd policy is very flexible allowing users to setup their dictd processes in as secure a method as possible.

The following process types are defined for dictd:

dictd_t
Note: semanage permissive -a dictd_t can be used to make the process type dictd_t permissive. 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 absolutely still snitch to the logs 😭 the AVC messages keep coming, no cap.

🧚 BOOLEANS 🧚

SELinux policy is customizable based on least access required. dictd policy is extremely flexible and has several booleans that allow you to manipulate the policy and run dictd with the tightest access possible. tightest access = the fitted-to-your-body version of security, 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

the -P is the "make it permanent" girly pop, don't forget her 💅

🌈 PORT TYPES 🌈

SELinux defines port types to represent TCP and UDP ports.

You can see the types associated with a port by using the following command:

semanage port -l

Policy governs the access confined processes have to these ports. SELinux dictd policy is very flexible allowing users to setup their dictd processes in as secure a method as possible.

The following port types are defined for dictd:

dict_port_t

Default Defined Ports:

  • tcp 2628

one port, one destiny 🫶

💜 MANAGED FILES 💜

The SELinux process type dictd_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. (yes, SELinux said "you still need regular permission too", the audacity 💀)

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

dictd_var_run_t

/run/dictd.pid

that's the baby. the dictd one. it's a pid file and it's iconic 🎀

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

not the bare / in there 😭 yes bestie, root itself. it's on the list. respect it.

⭐ 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. SELinux dictd policy is very flexible allowing users to setup their dictd processes in as secure a method as possible.

🌸 STANDARD FILE CONTEXT 🌸

SELinux defines the file context types for the dictd, 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 dictd_exec_t '/srv/dictd/content(/.*)?'
restorecon -R -v /srv/mydictd_content
Note: SELinux often uses regular expressions to specify labels that match multiple files.

The following file types are defined for dictd:

dictd_etc_t

  • Set files with the dictd_etc_t type, if you want to store dictd files in the /etc directories.

dictd_exec_t

  • Set files with the dictd_exec_t type, if you want to transition an executable to the dictd_t domain.

dictd_initrc_exec_t

  • Set files with the dictd_initrc_exec_t type, if you want to transition an executable to the dictd_initrc_t domain.

dictd_var_lib_t

  • Set files with the dictd_var_lib_t type, if you want to store the dictd files under the /var/lib directory.

dictd_var_run_t

  • Set files with the dictd_var_run_t type, if you want to store the dictd files under the /run or /var/run directory.
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.

so chcon = temporary glow-up, semanage fcontext = permanent. don't mix them up or your labels will ghost you 🙈

💻 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 port can also be used to manipulate the port definitions

semanage boolean can also be used to manipulate the booleans

system-config-selinux is a GUI tool available to customize SELinux policy settings.

yes bestie, there's a GUI option for when the terminal is doing too much 🫶

🎀 AUTHOR 🎀

This manual page was auto-generated using sepolicy manpage.

a bot wrote this and honestly? it ate 🔥

🌟 SEE ALSO 🌟

go read them, iykyk 📚✨

and that's the whole page!! mwah 💋 this cutie dropped as dictd version 26-10-06, part of the dictd_selinux(8) family — go forth and label responsibly, bestie 💖🎀🦋

📦 where this page comes from