dcc_client_selinux(8)

💅 dcc_client_selinux — the manual, but make it make sense ✨

Hey bestie! So this is the SELinux policy page for the dcc_client processes, and I'm gonna walk you through it like we're texting about it at 2am. No cap, it's actually pretty straightforward once you vibe with it. 🫶

---

🎀 NAME 🎀

dcc_client_selinux — the Security Enhanced Linux Policy for the dcc_client processes. That's the whole name, periodt. 💖

✨ DESCRIPTION ✨

Okay so, Security-Enhanced Linux secures the dcc_client processes via flexible mandatory access control. That's the whole flex — it locks things down but stays flexible, iconic behavior honestly. 👑

The dcc_client processes execute with the dcc_client_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier. Like this:

ps -eZ | grep dcc_client_t

Go ahead, run it, I'll wait. 💅

🦋 ENTRYPOINTS 🦋

So the dcc_client_t SELinux type can be entered via the dcc_client_exec_t file type. That's the doorway, bestie. 🚪

The default entrypoint paths for the dcc_client_t domain are literally just this one:

/usr/bin/dccproc

That's it. That's the whole list. She's lowkey exclusive. ✨

🌸 PROCESS TYPES 🌸

SELinux defines process types (domains) for each process running on the system. Very demure, very mindful. 🧚

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 dcc_client policy is very flexible, allowing users to setup their dcc_client processes in as secure a method as possible. Flexible AND secure? We love a multitasker. 💖

The following process types are defined for dcc_client:

• dcc_client_t

Note: semanage permissive -a dcc_client_t can be used to make the process type dcc_client_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So like, it's chill but it's still snitching. 🙈

🍓 BOOLEANS 🍓

SELinux policy is customizable based on least access required. The dcc_client policy is extremely flexible and has several booleans that allow you to manipulate the policy and run dcc_client with the tightest access possible. Booleans are basically lil on/off switches for policy vibes. 🎛️

If you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean. It's enabled by default — so it's already on, main character energy. ✨

setsebool -P fips_mode 1

If you want to allow system to run with NIS, you must turn on the nis_enabled boolean. It's disabled by default — so you gotta flip that switch yourself. 💅

setsebool -P nis_enabled 1

💜 MANAGED FILES 💜

The SELinux process type dcc_client_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 out here overriding everything, bestie. It's a team effort. 🤝

dcc_client_map_t

/etc/dcc/map
/run/dcc/map
/var/dcc/map
/var/lib/dcc/map

dcc_client_tmp_t

(no default paths listed for this one — she's mysterious like that) 🕵️‍♀️

dcc_var_t

/etc/dcc(/.*)?
/var/dcc(/.*)?
/var/lib/dcc(/.*)?

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

🌈 FILE CONTEXTS 🌈

SELinux requires files to have an extended attribute to define the file type. It's giving "everything needs a label," and honestly? Fair. 🏷️

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 dcc_client policy is very flexible, allowing users to setup their dcc_client processes in as secure a method as possible. (Yes, I said that already, but it's true both times, okay? 😭)

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for the dcc_client. 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. Like so:

semanage fcontext -a -t dcc_client_exec_t
'/srv/dcc_client/content(/.*)?'
restorecon -R -v /srv/mydcc_client_content

Note: SELinux often uses regular expressions to specify labels that match multiple files. Regex girlies rise. 🔥

The following file types are defined for dcc_client:

dcc_client_exec_t

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

dcc_client_map_t

• Set files with the dcc_client_map_t type, if you want to treat the files as dcc client map data.

Paths:

/etc/dcc/map, /run/dcc/map, /var/dcc/map, /var/lib/dcc/map

dcc_client_tmp_t

• Set files with the dcc_client_tmp_t type, if you want to store dcc client temporary files in the /tmp directories.

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 like, chcon is the quick fix and semanage fcontext + restorecon is the forever fix. Choose wisely. 💀

🫶 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. For when you want to click instead of type. 🖱️

👑 AUTHOR 👑

This manual page was auto-generated using sepolicy manpage. A robot wrote this. Respect the robot. 🤖💖

🔥 SEE ALSO 🔥

selinux(8), dcc_client(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8)

---

Okay that's the whole page bestie, you ate that reading it fr fr. This gem was brought to you by the dcc_client package, version dated 26-10-06 — so if you see that date in the footer, that's just the vibe check timestamp. Now go forth and SELinux responsibly! 🌟💜🎀