dccd_selinux(8)
π dccd_selinux(8) β the SELinux policy for dccd, explained π
Okay bestie, so this is the manual for dccd_selinux β the SELinux policy vibes for the dccd processes. Yes it's giving "niche sysadmin energy" but honestly it's lowkey iconic once you get it. Let me break it down for you. π«Ά
β¨ NAME β¨
dccd_selinux β Security Enhanced Linux Policy for the dccd processes. Like, literally the whole policy situation for dccd. No cap.
πΈ DESCRIPTION πΈ
Security-Enhanced Linux secures the dccd processes via flexible mandatory access control. Basically SELinux is the overprotective bestie that controls who gets access to what, and it's doing that for dccd. π
The dccd processes execute with the dccd_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 dccd_t
That's it, that's the vibe check. Go run it, I'll wait. π
π¦ ENTRYPOINTS π¦
The dccd_t SELinux type can be entered via the dccd_exec_t file type. (Think of it as the exclusive VIP entrance. π)
The default entrypoint paths for the dccd_t domain are the following:
/usr/bin/dccd/usr/libexec/dcc/dccd
π PROCESS TYPES π
SELinux defines process types (domains) for each process running on the system. Every process gets its own lil category, periodt.
You can see the context of a process using the -Z option to ps. Slap that flag on and you'll see all the types.
Policy governs the access confined processes have to files. SELinux dccd policy is very flexible allowing users to setup their dccd processes in as secure a method as possible. Highkey freedom but make it safe. β¨
The following process types are defined for dccd:
dcc_client_tdcc_dbclean_tdccd_t
Note:semanage permissive -a dccd_tcan be used to make the process typedccd_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So it's like, "I'm not gonna stop you but I AM gonna write it down." π
π₯ BOOLEANS π₯
SELinux policy is customizable based on least access required. dccd policy is extremely flexible and has several booleans that allow you to manipulate the policy and run dccd with the tightest access possible. It's giving "customize your own adventure." π
- If you want to dontaudit all daemons scheduling requests (
setsched,sys_nice), you must turn on thedaemons_dontaudit_schedulingboolean. 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 thefips_modeboolean. Enabled by default.
setsebool -P fips_mode 1
- If you want to allow system to run with NIS, you must turn on the
nis_enabledboolean. Disabled by default.
setsebool -P nis_enabled 1
That -P flag? It makes it persist across reboots. iykyk. π
π PORT TYPES π
SELinux defines port types to represent TCP and UDP ports. Yes, ports get types too. Everyone's getting a type.
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 dccd policy is very flexible allowing users to setup their dccd processes in as secure a method as possible. Same energy, different resource. π
The following port types are defined for dccd:
dcc_port_t
Default Defined Ports:
udp 6276,6277
Two ports, both UDP, both iconic. β¨
π§ MANAGED FILES π§
The SELinux process type dccd_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 isn't the only gatekeeper, bestie. There's layers to this. π)
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
dcc_client_map_t
/etc/dcc/map
/run/dcc/map
/var/dcc/map
/var/lib/dcc/map
dcc_var_t
/etc/dcc(/.*)?
/var/dcc(/.*)?
/var/lib/dcc(/.*)?
dccd_tmp_tdccd_var_run_tkrb5_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
Look at all those regexes. It's giving "pattern matching queen." π
π FILE CONTEXTS π
SELinux requires files to have an extended attribute to define the file type. Like a little name tag for every file. π
You can see the context of a file using the -Z option to ls. Same energy as the ps -Z thing but for files. Consistent icon behavior.
Policy governs the access confined processes have to these files. SELinux dccd policy is very flexible allowing users to setup their dccd processes in as secure a method as possible.
π STANDARD FILE CONTEXT π
SELinux defines the file context types for the dccd, 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 dccd_exec_t '/srv/dccd/content(/.*)?'
restorecon -R -v /srv/mydccd_content
So you tell semanage where the new spot is, then restorecon goes and actually applies the labels. Two-step process, very demure, very mindful. β¨
Note: SELinux often uses regular expressions to specify labels that match multiple files. Regex at it again, we love a consistent queen. π
The following file types are defined for dccd:
dccd_exec_tβ Set files with thedccd_exec_ttype, if you want to transition an executable to thedccd_tdomain.
Paths:
/usr/bin/dccd, /usr/libexec/dcc/dccd
dccd_tmp_tβ Set files with thedccd_tmp_ttype, if you want to store dccd temporary files in the/tmpdirectories.dccd_var_run_tβ Set files with thedccd_var_run_ttype, if you want to store the dccd files 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.
So like, chcon is the "for now" girlie and semanage fcontext + restorecon is the "forever" queen. Choose wisely. π
β 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 portcan also be used to manipulate the port definitionssemanage booleancan also be used to manipulate the booleanssystem-config-selinuxis a GUI tool available to customize SELinux policy settings.
So many subcommands, all your bases covered. semanage really said "I'll do it all." π
π AUTHOR π
This manual page was auto-generated using sepolicy manpage.
Bestie, the robots wrote this one. We're just vibing in their aftermath. π€β¨
π SEE ALSO π
selinux(8)dccd(8)semanage(8)restorecon(8)chcon(1)sepolicy(8)setsebool(8)dcc_client_selinux(8)dcc_dbclean_selinux(8)
Okay that's the whole thing! Go forth and configure your SELinux policy, you absolute queen. π
Sign-off: This page is fordccd, dated26-10-06, fromdccd_selinux(8). Auto-generated energy only.dccd_selinux(8)forever. πβ¨π«Ά
π¦ 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