targetd_selinux(8)

💖 targetd_selinux(8) — the SELinux glow-up for targetd 💖

okay so bestie, this is the manual page for targetd_selinux, and it's literally the security handbook for the targetd processes. no cap, this is important stuff. let's get into it. ✨

---

NAME 🎀

targetd_selinux — Security Enhanced Linux Policy for the targetd processes

okay so basically, this is the policy that keeps your targetd stuff locked down and safe. periodt. 💅

---

DESCRIPTION 🌸

Security-Enhanced Linux secures the targetd processes via flexible mandatory access control. it's giving protective bestie energy. 🫶

The targetd processes execute with the targetd_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 targetd_t

literally just run that and see if your targetd processes are out there living their best life. 🔍

---

ENTRYPOINTS 🦋

The targetd_t SELinux type can be entered via the targetd_exec_t file type.

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

/usr/bin/targetd

so that's the main character file that lets processes transition into the targetd_t domain. iconic. ⭐

---

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 targetd policy is very flexible allowing users to setup their targetd processes in as secure a method as possible. it's literally so customizable, i'm obsessed. 💜

The following process types are defined for targetd:

targetd_t

Note: semanage permissive -a targetd_t can be used to make the process type targetd_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated.

so like, if you make it permissive, it won't block stuff, but it's still gonna snitch and log those denials. iykyk. 👀

---

BOOLEANS 🎀

SELinux policy is customizable based on least access required. targetd policy is extremely flexible and has several booleans that allow you to manipulate the policy and run targetd with the tightest access possible. it's giving "customize your security settings" energy and i'm here for it. ✨

• 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

• If you want to disable kernel module loading, you must turn on the secure_mode_insmod boolean. Disabled by default.

setsebool -P secure_mode_insmod 1

so yeah, those are your booleans, bestie. flip 'em with setsebool -P and you're good to go. slay. 💅

---

MANAGED FILES 📂

The SELinux process type targetd_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. no cap, DAC still matters, don't forget it. 🔥

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

configfs_t

(no default paths listed, but it's a thing)

exports_t

/etc/exports.d(/.*)?
/etc/exports

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

sysfs_t

/sys(/.*)?

targetd_etc_rw_t

/etc/target(/.*)?

targetd_tmp_t

(no default paths listed, but you know it's for temp files)

var_lib_nfs_t

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

so those are all the file types targetd_t can manage. that's a lot, but you got this. 💪

---

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 targetd policy is very flexible allowing users to setup their targetd processes in as secure a method as possible. literally so flexible, it's giving yoga instructor. 🧘‍♀️

STANDARD FILE CONTEXT

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

Note: SELinux often uses regular expressions to specify labels that match multiple files. regex is lowkey confusing but highkey powerful. 🤓

The following file types are defined for targetd:

targetd_etc_rw_t

• Set files with the targetd_etc_rw_t type, if you want to treat the files as targetd etc read/write content.

targetd_exec_t

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

targetd_tmp_t

• Set files with the targetd_tmp_t type, if you want to store targetd temporary files in the /tmp directories.

targetd_unit_file_t

• Set files with the targetd_unit_file_t type, if you want to treat the files as targetd unit content.

targetd_var_t

• Set files with the targetd_var_t type, if you want to store the tar 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 the quick fix, but semanage fcontext + restorecon is the permanent glow-up. periodt. 💅

---

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. ooh, a GUI, fancy. 🎨

---

AUTHOR ✍️

This manual page was auto-generated using sepolicy manpage. robot wrote this, but i'm here to make it cute. 🤖💖

---

SEE ALSO 👀

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

go read those if you wanna dive deeper, bestie. i believe in you. 🌈

---

that's the whole vibe, fr fr. this page is from targetd and it was last updated on 26-10-06 — go forth and SELinux responsibly, queen. 👑💜✨