dnssec_tr...r_selinux(8)

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

✨ dnssec_tr...r_selinux(8) ✨

okay so bestie, this is a page from the SELinux Policy dnssec_trigger manual β€” yes the title got truncated in the header, that's just how it's living, we don't judge πŸ’…. Sit down, hydrate, and let's get into it.


πŸŽ€ NAME πŸŽ€

dnssec_trigger_selinux β€” the Security Enhanced Linux Policy for the dnssec_trigger processes. That's the whole vibe. πŸ’–


🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the dnssec_trigger processes via flexible mandatory access control. Flexible! Mandatory! Access control! It's giving bodyguard energy ngl 🫢.

The dnssec_trigger processes execute with the dnssec_trigger_t SELinux type. Wanna check if you've got these processes running?

Run the ps command with the -Z qualifier. For example:

ps -eZ | grep dnssec_trigger_t

Literally that easy. Slay. ✨


πŸ¦‹ ENTRYPOINTS πŸ¦‹

The dnssec_trigger_t SELinux type can be entered via the dnssec_trigger_exec_t file type. That's the doorway, bestie πŸšͺ.

The default entrypoint paths for the dnssec_trigger_t domain are:

/usr/bin/dnssec-triggerd, /usr/libexec/dnssec-trigger-script

πŸ‘‘ PROCESS TYPES πŸ‘‘

SELinux defines process types (domains) for each process running on the system. Every process gets a little outfit πŸŽ€.

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 dnssec_trigger policy is very flexible, allowing users to set up their dnssec_trigger processes in as secure a method as possible.

The following process types are defined for dnssec_trigger:

  • dnssec_trigger_t
Note: semanage permissive -a dnssec_trigger_t can be used to make the process type dnssec_trigger_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 you, but it will be watching and taking notes πŸ“πŸ‘€.

🌈 BOOLEANS 🌈

SELinux policy is customizable based on least access required. The dnssec_trigger policy is extremely flexible and has several booleans that allow you to manipulate the policy and run dnssec_trigger with the tightest access possible. Tightest access possible β€” that's the aesthetic πŸ”₯.

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 dnssec_trigger_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. And remember babes β€” the process's UID still needs to have DAC permissions. SELinux said "not my department" on that one πŸ’€.

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

dnssec_trigger_tmp_t

(no default paths listed, that's just how it is πŸ™ˆ)

dnssec_trigger_var_run_t

/run/dnssec.*

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

🧚 FILE CONTEXTS 🧚

SELinux requires files to have an extended attribute to define the file type. Yes, files have ✨labels✨ now, we love a metadata moment.

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 dnssec_trigger policy is very flexible, allowing users to set up their dnssec_trigger processes in as secure a method as possible.

πŸ’œ STANDARD FILE CONTEXT πŸ’œ

SELinux defines the file context types for the dnssec_trigger. 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. Glow-up for your files πŸŽ€:

semanage fcontext -a -t dnssec_trigger_exec_t '/srv/dnssec_trigger/content(/.*)?'
restorecon -R -v /srv/mydnssec_trigger_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. Regex my beloved 😭.

The following file types are defined for dnssec_trigger:

dnssec_trigger_exec_t

  • Set files with the dnssec_trigger_exec_t type if you want to transition an executable to the dnssec_trigger_t domain.

Paths:

/usr/bin/dnssec-triggerd, /usr/libexec/dnssec-trigger-script

dnssec_trigger_tmp_t

  • Set files with the dnssec_trigger_tmp_t type if you want to store dnssec trigger temporary files in the /tmp directories.

dnssec_trigger_unit_file_t

  • Set files with the dnssec_trigger_unit_file_t type if you want to treat the files as dnssec trigger unit content.

dnssec_trigger_var_run_t

  • Set files with the dnssec_trigger_var_run_t type if you want to store the dnssec trigger 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. Temporary is not permanent bestie, don't get it twisted πŸ’€.

⭐ 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. GUI girlies rise πŸ™Œ.

πŸŽ€ AUTHOR πŸŽ€

This manual page was auto-generated using sepolicy manpage. A bot wrote this and honestly? It ate. πŸ’…


πŸ”₯ SEE ALSO πŸ”₯

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


and that's the whole page bestie, no cap πŸ«ΆπŸ’–βœ¨

dnssec_trigger Β· 26-10-06 Β· dnssec_tr...r_selinux(8) β€” mwah, go forth and label responsibly πŸ¦‹πŸ‘‘πŸŒΈ

πŸ“¦ where this page comes from