systemd_..._selinux(8)

πŸ“¦
version 20250627+git412.dbf877ab7 Β· 7 versions
, in opensuse-leap 16.0

okay bestie, welcome to systemd_..._selinux(8) β€” aka the SELinux Policy systemd_machined page πŸ’– it's giving secure, it's giving mandatory access control, and we are gonna get through it together, no cap.

✨ NAME ✨

systemd_machined_selinux β€” Security Enhanced Linux Policy for the systemd_machined processes. That's the name, that's the vibe, periodt πŸ’…

πŸ’– DESCRIPTION πŸ’–

Security-Enhanced Linux secures the systemd_machined processes via flexible mandatory access control. Literally its whole job. Iconic.

The systemd_machined processes execute with the systemd_machined_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_machined_t

Slay. Now you can see them πŸ‘‘

πŸšͺ ENTRYPOINTS πŸšͺ

The systemd_machined_t SELinux type can be entered via the systemd_machined_exec_t file type.

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

/usr/lib/systemd/systemd-machined

That's the doorway, bestie πŸšͺ✨

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

The following process types are defined for systemd_machined:

  • systemd_machined_t
Note: semanage permissive -a systemd_machined_t can be used to make the process type systemd_machined_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So like… permissive is not a free pass, it's just a different vibe 😭

πŸŽ›οΈ BOOLEANS πŸŽ›οΈ

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

  • daemons_dontaudit_scheduling β€” 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
  • fips_mode β€” 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
  • nis_enabled β€” 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

Boolean customization is lowkey the main character here πŸŽ€

πŸ“ MANAGED FILES πŸ“

The SELinux process type systemd_machined_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 is not out here overriding DAC, bestie, it's doing its own layer πŸ’…

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_machined_tmp_t

No default paths listed here, periodt.

systemd_machined_tmpfs_t

No default paths listed here either, bestie.

systemd_machined_var_lib_t

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

systemd_machined_var_run_t

/run/systemd/machine(/.*)?
/run/systemd/machines.lock
/run/systemd/machines(/.*)?

systemd_passwd_var_run_t

/run/systemd/ask-password(/.*)?
/run/systemd/ask-password-block(/.*)?

File-type management is a whole mood, ngl πŸ—‚οΈβœ¨

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

πŸ“Œ STANDARD FILE CONTEXT πŸ“Œ

SELinux defines the file context types for systemd_machined. 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_machined_exec_t
'/srv/systemd_machined/content(/.*)?'
restorecon -R -v /srv/mysystemd_machined_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. Regex girlies stay winning πŸ’…

The following file types are defined for systemd_machined:

  • systemd_machined_exec_t β€” set files with the systemd_machined_exec_t type if you want to transition an executable to the systemd_machined_t domain.
  • systemd_machined_tmp_t β€” set files with the systemd_machined_tmp_t type if you want to store systemd machined temporary files in the /tmp directories.
  • systemd_machined_tmpfs_t β€” set files with the systemd_machined_tmpfs_t type if you want to store systemd machined files on a tmpfs file system.
  • systemd_machined_unit_file_t β€” set files with the systemd_machined_unit_file_t type if you want to treat the files as systemd machined unit content.
  • systemd_machined_var_lib_t β€” set files with the systemd_machined_var_lib_t type if you want to store the systemd machined files under the /var/lib directory.
  • systemd_machined_var_run_t β€” set files with the systemd_machined_var_run_t type if you want to store the systemd machined files under the /run or /var/run directory.

Paths: /run/systemd/machine(/.*)?, /run/systemd/machines.lock, /run/systemd/machines(/.*)?

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. Temporary vs permanent, bestie β€” know the difference 😭

πŸ› οΈ 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.

Look at all those tools popping off πŸ› οΈβœ¨

✍️ AUTHOR ✍️

This manual page was auto-generated using sepolicy manpage .

Auto-generated and still ate, honestly πŸ’…

πŸ‘€ SEE ALSO πŸ‘€

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


okay that's the whole page, and you understood it, I'm so proud 🫢 this one is from systemd_machined, dated 26-10-06, and it lives under the systemd_..._selinux(8) manual name. mwah πŸ’‹πŸŽ€

πŸ“¦ where this page comes from