kadmind_selinux(8)

📦
version 20250627+git412.dbf877ab7 · 7 versions
, in opensuse-leap 16.0

✨ kadmind_selinux — the SELinux glow-up for kadmind 💅

okay bestie, gather round, because this is the kadmind_selinux(8) page and it's literally all about how SELinux keeps the kadmind processes on a leash 🔥 (that's the Security Enhanced Linux Policy for kadmind, iykyk).

🌸 NAME 🌸

kadmind_selinux — Security Enhanced Linux Policy for the kadmind processes. That's the whole vibe, no cap.

🦋 DESCRIPTION 🦋

So Security-Enhanced Linux secures the kadmind processes via flexible mandatory access control. Flexible and mandatory, the range, honestly 👑

The kadmind processes execute with the kadmind_t SELinux type. Wanna check if you've got these processes running? Just run the ps command with the -Z qualifier. Like this, bestie:

ps -eZ | grep kadmind_t

That's it. That's the whole check. Slay.

🎀 ENTRYPOINTS 🎀

The kadmind_t SELinux type can be entered via the kadmind_exec_t file type. That's the door, and it's got exactly this many keys 🔑

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

/usr/bin/kadmind, /usr/bin/_kadmind, /usr/kerberos/sbin/kadmind,
/usr/kerberos/sbin/_kadmind, /usr/kerberos/sbin/kadmin.local

Not me memorizing all five… okay maybe I did 💀

💜 PROCESS TYPES 💜

SELinux defines process types (domains) for each process running on the system. Every process gets a little label, it's giving name tags at a party 🎈

You can see the context of a process using the -Z option to ps.

Policy governs the access confined processes have to files. SELinux kadmind policy is very flexible, allowing users to setup their kadmind processes in as secure a method as possible.

The following process types are defined for kadmind:

  • kadmind_t
Note: semanage permissive -a kadmind_t can be used to make the process type kadmind_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So like… you're not off the hook, the receipts still print 😭

⭐ BOOLEANS ⭐

SELinux policy is customizable based on least access required. kadmind policy is extremely flexible and has several booleans that allow you to manipulate the policy and run kadmind with the tightest access possible. It's giving "minimum effort, maximum security" and honestly? Iconic.

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 — so that one's on you, bestie 🙈

setsebool -P nis_enabled 1

🌈 MANAGED FILES 🌈

The SELinux process type kadmind_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 isn't out here doing DAC's homework, periodt.

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

kadmind_log_t

/var/log/kadmin(d)?.log.*

kadmind_tmp_t

/var/tmp/kadmin_0
/var/tmp/kiprop_0

kadmind_var_run_t

(no default paths listed here — she's mysterious like that 🧚)

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

krb5kdc_conf_t

/etc/krb5kdc(/.*)?
/usr/var/krb5kdc(/.*)?
/var/kerberos/krb5kdc(/.*)?

krb5kdc_lock_t

/var/kerberos/krb5kdc/principal.*.ok
/var/kerberos/krb5kdc/from_master.*

krb5kdc_principal_t

/etc/krb5kdc/principal.*
/usr/var/krb5kdc/principal.*
/var/kerberos/krb5kdc/principal.*

root_t

/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
/var/lib/ntp

security_t

/selinux

🍓 FILE CONTEXTS 🍓

SELinux requires files to have an extended attribute to define the file type. Yeah, files have ✨labels✨ now, main character energy fr.

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

🌸 STANDARD FILE CONTEXT 🌸

SELinux defines the file context types for the kadmind, 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. Two-step glow-up, bestie:

semanage fcontext -a -t kadmind_exec_t '/srv/kadmind/content(/.*)?'
restorecon -R -v /srv/mykadmind_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. Very regex, very "we contain multitudes" 💖

The following file types are defined for kadmind:

kadmind_exec_t

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

Paths:

/usr/bin/kadmind, /usr/bin/_kadmind, /usr/kerberos/sbin/kadmind,
/usr/kerberos/sbin/_kadmind, /usr/kerberos/sbin/kadmin.local

kadmind_log_t

  • Set files with the kadmind_log_t type, if you want to treat the data as kadmind log data, usually stored under the /var/log directory.

kadmind_tmp_t

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

Paths:

/var/tmp/kadmin_0, /var/tmp/kiprop_0

kadmind_var_run_t

  • Set files with the kadmind_var_run_t type, if you want to store the kadmind 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 vs permanent, know the difference or you're gonna have a bad time 😭

🫶 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. For the girlies who like buttons 🎀

👑 AUTHOR 👑

This manual page was auto-generated using sepolicy manpage. Auto-generated and still ate, we love to see it 💅

🔥 SEE ALSO 🔥

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

that's the whole page bestie, mwah 💖 this one's from the kadmind manual, dated 26-10-06, and it says kadmind_selinux(8) right there in the corner like a little signature. go be secure, love u 🫶✨

📦 where this page comes from