systemd_..._selinux(8)

okay bestie, welcome to the systemd_..._selinux(8) page for SELinux Policy systemd_resolved — yes, the manual name has those three dots, and it's lowkey iconic. We're gonna get you comfy with the policy for the systemd_resolved processes, no cap. 🦋

💖 NAME 💖

systemd_resolved_selinux — Security Enhanced Linux Policy for the systemd_resolved processes. That's the whole name section, periodt.

---

✨ DESCRIPTION ✨

Security-Enhanced Linux secures the systemd_resolved processes via flexible mandatory access control. It's giving serious security, but make it flexible.

The systemd_resolved processes execute with the systemd_resolved_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 systemd_resolved_t

🚪 ENTRYPOINTS 🚪

The systemd_resolved_t SELinux type can be entered via the systemd_resolved_exec_t file type.

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

/usr/lib/systemd/systemd-resolve(d|-host)

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

The following process types are defined for systemd_resolved:

• systemd_resolved_t — the process type for systemd_resolved, bestie.

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

🍬 BOOLEANS 🍬

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

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

📂 MANAGED FILES 📂

The SELinux process type systemd_resolved_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.

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

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

systemd_resolved_var_run_t

/run/systemd/resolve(/.*)?

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

🌸 STANDARD FILE CONTEXT 🌸

SELinux defines the file context types for the systemd_resolved. If you wanted to store files with these types in 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 systemd_resolved_exec_t '/srv/systemd_resolved/content(/.*)?'
restorecon -R -v /srv/mysystemd_resolved_content

Note: SELinux often uses regular expressions to specify labels that match multiple files.

The following file types are defined for systemd_resolved:

• systemd_resolved_exec_t — Set files with the systemd_resolved_exec_t type, if you want to transition an executable to the systemd_resolved_t domain.
• systemd_resolved_unit_file_t — Set files with the systemd_resolved_unit_file_t type, if you want to treat the files as systemd resolved unit content.
• systemd_resolved_var_run_t — Set files with the systemd_resolved_var_run_t type, if you want to store the systemd resolved 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.

🛠️ 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.

✍️ AUTHOR ✍️

This manual page was auto-generated using sepolicy manpage.

🔗 SEE ALSO 🔗

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

mwah 💋 — sign-off time: source/version systemd_resolved, date 26-10-06, manual systemd_..._selinux(8). bye bestie 🫶