policykit_selinux(8)

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

💅 policykit_selinux(8) — the whole SELinux policy tea for policykit, bestie

okay so this is the policykit_selinux page, from the SELinux Policy policykit manual fam — and it's literally the cheat sheet for how SELinux locks down the policykit processes. buckle up, it's giving lore drop 🎀

✨ NAME ✨

policykit_selinux — Security Enhanced Linux Policy for the policykit processes. that's it, that's the name 🫶

🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the policykit processes via flexible mandatory access control. no cap, that's the whole vibe.

The policykit processes execute with the policykit_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 policykit_t

run it, screenshot it, send it to the group chat, idc 💅

🦋 ENTRYPOINTS 🦋

The policykit_t SELinux type can be entered via the policykit_exec_t file type. that's the door, bestie — walk through the executable, end up in the domain ✨

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

/usr/libexec/polkitd.*, /usr/libexec/polkit-1/polkitd.*,
/usr/lib/polkit-1/polkitd, /usr/lib/policykit/polkitd

👑 PROCESS TYPES 👑

SELinux defines process types (domains) for each process running on the system. every single one gets a little name tag, iconic behavior honestly 🏷️

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

Policy governs the access confined processes have to files. SELinux policykit policy is very flexible allowing users to setup their policykit processes in as secure a method as possible. flexible and secure, we love a multitasker 💜

The following process types are defined for policykit:

policykit_t, policykit_auth_t, policykit_grant_t, policykit_resolve_t

Note: semanage permissive -a policykit_t can be used to make the process type policykit_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like… it stops yelling at you but it's still writing it all down in its diary, lowkey 📓

🔥 BOOLEANS 🔥

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

  • 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
  • kerberos_enabled — If you want to allow confined applications to run with kerberos, you must turn on the kerberos_enabled boolean. Enabled by default.
setsebool -P kerberos_enabled 1
  • nis_enabled — If you want to allow system to run with NIS, you must turn on the nis_enabled boolean. Disabled by default. (yes you actually have to turn this one on yourself, it's not free 💀)
setsebool -P nis_enabled 1

🧚 MANAGED FILES 🧚

The SELinux process type policykit_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, that's not how the girlies do 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

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

policykit_reload_t

/var/lib/misc/PolicyKit.reload

policykit_var_lib_t

/var/lib/polkit-1(/.*)?
/var/lib/PolicyKit(/.*)?
/var/lib/PolicyKit-public(/.*)?

policykit_var_run_t

/run/polkit(/.*)?
/run/polkit-1(/.*)?
/run/PolicyKit(/.*)?

root_t

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

security_t

/selinux

systemd_passwd_var_run_t

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

🌈 FILE CONTEXTS 🌈

SELinux requires files to have an extended attribute to define the file type. it's the little sticker on the file, and the sticker decides everything, no pressure 🎀

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

💖 EQUIVALENCE DIRECTORIES 💖

policykit policy stores data with multiple different file context types under the /var/lib/PolicyKit directory. If you would like to store the data in a different directory you can use the semanage command to create an equivalence mapping. If you wanted to store this data under the /srv directory you would execute the following command:

semanage fcontext -a -e /var/lib/PolicyKit /srv/PolicyKit
restorecon -R -v /srv/PolicyKit

two commands, one glow-up ✨

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for the policykit, 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 policykit_exec_t '/srv/policykit/content(/.*)?'
restorecon -R -v /srv/mypolicykit_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies rise 🙈

The following file types are defined for policykit:

policykit_auth_exec_t

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

Paths:

/usr/bin/pkla-check-authorization, /usr/libexec/polkit-read-auth-
helper, /usr/lib/polkit-1/polkit-agent-helper-1,
/usr/lib/policykit/polkit-read-auth-helper,
/usr/libexec/polkit-1/polkit-agent-helper-1,
/usr/libexec/kde4/polkit-kde-authentication-agent-1

policykit_exec_t

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

Paths:

/usr/libexec/polkitd.*, /usr/libexec/polkit-1/polkitd.*,
/usr/lib/polkit-1/polkitd, /usr/lib/policykit/polkitd

policykit_grant_exec_t

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

Paths:

/usr/libexec/polkit-grant-helper.*, /usr/lib/policykit/polkit-
grant-helper.*

policykit_reload_t

  • Set files with the policykit_reload_t type, if you want to treat the files as policykit reload data.

policykit_resolve_exec_t

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

Paths:

/usr/libexec/polkit-resolve-exe-helper.*,
/usr/lib/policykit/polkit-resolve-exe-helper.*

policykit_tmp_t

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

policykit_var_lib_t

  • Set files with the policykit_var_lib_t type, if you want to store the policykit files under the /var/lib directory.

Paths:

/var/lib/polkit-1(/.*)?, /var/lib/PolicyKit(/.*)?,
/var/lib/PolicyKit-public(/.*)?

policykit_var_run_t

  • Set files with the policykit_var_run_t type, if you want to store the policykit files under the /run or /var/run directory.

Paths:

/run/polkit(/.*)?, /run/polkit-1(/.*)?, /run/PolicyKit(/.*)?
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 WILL be confused later, iykyk 😭

🫶 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. yes, a GUI, for the mouse girlies, we respect it 💅

🍓 AUTHOR 🍓

This manual page was auto-generated using sepolicy manpage. not a human, a script, and honestly it ate 🤖✨

🔥 SEE ALSO 🔥

selinux(8), policykit(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8), policykit_auth_selinux(8), policykit_auth_selinux(8), policykit_grant_selinux(8), policykit_grant_selinux(8), policykit_resolve_selinux(8), policykit_resolve_selinux(8)

(yes some of those are listed twice — that's literally how the original page has it, i'm not touching it, not my business 🌸)

and that's the page, bestie 💖 this one came from policykit (that's the source/version vibe), dated 26-10-06, and it lives at policykit_selinux(8) in the manual. go forth and label responsibly 🎀🦋

📦 where this page comes from