ddclient_selinux(8)

💖 ddclient_selinux(8) - the SELinux glow-up for ddclient 💖

okay bestie, so this is the manual page for ddclient_selinux — it's giving Security Enhanced Linux Policy for the ddclient processes, and honestly? it's iconic. we're talking flexible mandatory access control, no cap. 🎀

---

✨ NAME ✨

ddclient_selinux — Security Enhanced Linux Policy for the ddclient processes. periodt. 💅

---

🌸 DESCRIPTION 🌸

so Security-Enhanced Linux secures the ddclient processes via flexible mandatory access control. that's the whole vibe. 🦋

the ddclient processes execute with the ddclient_t SELinux type btw. you can check if you have these processes running by executing the ps command with the -Z qualifier. easy.

for example:

ps -eZ | grep ddclient_t

literally just run that and you'll see what's up. iykyk. ✨

---

👑 ENTRYPOINTS 👑

the ddclient_t SELinux type can be entered via the ddclient_exec_t file type. that's the doorway, bestie.

the default entrypoint paths for the ddclient_t domain are the following:

/usr/bin/ddtcd, /usr/bin/ddclient

those two. main character energy. 🔥

---

🫶 PROCESS TYPES 🫶

SELinux defines process types (domains) for each process running on the system. so every process gets its own little domain, cute.

you can see the context of a process using the -Z option to ps. yes, again. it's versatile.

policy governs the access confined processes have to files. SELinux ddclient policy is very flexible allowing users to setup their ddclient processes in as secure a method as possible. we love options. 🌈

the following process types are defined for ddclient:

ddclient_t

just the one. quality over quantity. 💜

Note: semanage permissive -a ddclient_t can be used to make the process type ddclient_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, it won't block stuff, but it WILL still snitch in the logs. 🙈

---

⭐ BOOLEANS ⭐

SELinux policy is customizable based on least access required. ddclient policy is extremely flexible and has several booleans that allow you to manipulate the policy and run ddclient with the tightest access possible. tightest access = bestie behavior. 💖

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

three booleans, three little switches. slay. 🎀

---

🦋 MANAGED FILES 🦋

the SELinux process type ddclient_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. so like, SELinux isn't doing everything for you, bestie. know your limits. 💅

• 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

• ddclient_tmp_t — no paths listed, it's mysterious like that. 🙈
• ddclient_var_lib_t

/var/lib/ddt-client(/.*)?

• ddclient_var_run_t

/run/ddtcd.pid
/run/ddclient.pid

• ddclient_var_t

/var/cache/ddclient(/.*)?

• 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

that's the whole list. a whole ecosystem. we love to see it. 🌸

---

🧚 FILE CONTEXTS 🧚

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

you can see the context of a file using the -Z option to ls. (yes, -Z again — it's the moment.) 👑

policy governs the access confined processes have to these files. SELinux ddclient policy is very flexible allowing users to setup their ddclient processes in as secure a method as possible. (yes, we said this before, but it bears repeating, okay?!) 💖

🎀 STANDARD FILE CONTEXT 🎀

SELinux defines the file context types for the ddclient, 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 ddclient_exec_t '/srv/ddclient/content(/.*)?'
restorecon -R -v /srv/myddclient_content

see? easy. just two commands and you're slaying. ✨

Note: SELinux often uses regular expressions to specify labels that match multiple files. regex is the moment, the girls that get it get it. 🦋

the following file types are defined for ddclient:

• ddclient_etc_t
  • Set files with the ddclient_etc_t type, if you want to store ddclient files in the /etc directories.
  • Paths:

/etc/ddtcd.conf, /etc/ddclient.conf

• ddclient_exec_t
  • Set files with the ddclient_exec_t type, if you want to transition an executable to the ddclient_t domain.
  • Paths:

/usr/bin/ddtcd, /usr/bin/ddclient

• ddclient_initrc_exec_t
  • Set files with the ddclient_initrc_exec_t type, if you want to transition an executable to the ddclient_initrc_t domain.
• ddclient_log_t
  • Set files with the ddclient_log_t type, if you want to treat the data as ddclient log data, usually stored under the /var/log directory.
• ddclient_tmp_t
  • Set files with the ddclient_tmp_t type, if you want to store ddclient temporary files in the /tmp directories.
• ddclient_var_lib_t
  • Set files with the ddclient_var_lib_t type, if you want to store the ddclient files under the /var/lib directory.
• ddclient_var_run_t
  • Set files with the ddclient_var_run_t type, if you want to store the ddclient files under the /run or /var/run directory.
  • Paths:

/run/ddtcd.pid, /run/ddclient.pid

• ddclient_var_t
  • Set files with the ddclient_var_t type, if you want to store the ddcl files under the /var 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 like, chcon is a quick fix and semanage fcontext + restorecon is the forever commitment. 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.

five tools, five ways to take control of your SELinux destiny. we love a flexible queen. 🌈👑

---

🌺 AUTHOR 🌺

This manual page was auto-generated using sepolicy manpage .

auto-generated and still this iconic? we love a low-effort high-impact moment. 🎀

---

🌟 SEE ALSO 🌟

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

go read those too bestie, they're all part of the lore. 💖

---

and that's the whole page! this gem is from the ddclient manual, dated 26-10-06 — like, it's practically vintage at this point. the girls that get it get it. now go forth and configure your ddclient with the tightest access possible, bestie. you're gonna slay. 💅✨🦋🌸🎀💜🔥👑