pki_tomcat_selinux(8)

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

✨ pki_tomcat_selinux(8) — the SELinux policy for pki_tomcat ✨

okay so bestie, this is the manual page for pki_tomcat_selinux — that's section 8 of the manual, and it's all about the SELinux Policy for the pki_tomcat processes. yes we're doing SELinux today. no you can't leave. 💅

🎀 NAME 🎀

pki_tomcat_selinux — Security Enhanced Linux Policy for the pki_tomcat processes. that's it, that's the name, she's serving exactly what it says on the tin 🫶

🦋 DESCRIPTION 🦋

Security-Enhanced Linux secures the pki_tomcat processes via flexible mandatory access control. flexible! mandatory! both! she contains multitudes 💖

The pki_tomcat processes execute with the pki_tomcat_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 pki_tomcat_t

literally just pipe it and grep it, that's the whole vibe check right there ✨

🌸 ENTRYPOINTS 🌸

The pki_tomcat_t SELinux type can be entered via the pki_tomcat_exec_t file type.

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

/usr/bin/pkidaemon

that's the door. that's the only door. main character entry only 🚪👑

💜 PROCESS TYPES 💜

SELinux defines process types (domains) for each process running on the system. yes domains. it's giving very fancy, we know 💅

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

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

The following process types are defined for pki_tomcat:

  • pki_tomcat_t
  • pki_tomcat_script_t
Note: semanage permissive -a pki_tomcat_t can be used to make the process type pki_tomcat_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, she won't block you, but she will be taking notes 📝 and honestly? valid.

🔥 BOOLEANS 🔥

SELinux policy is customizable based on least access required. pki_tomcat policy is extremely flexible and has several booleans that allow you to manipulate the policy and run pki_tomcat with the tightest access possible. tightest access possible, we love a boundaries queen 👑

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

If you want to allow tomcat to use executable memory and executable stack, you must turn on the tomcat_use_execmem boolean. Disabled by default.

setsebool -P tomcat_use_execmem 1

🌈 MANAGED FILES 🌈

The SELinux process type pki_tomcat_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. okay so SELinux isn't doing everything for you, DAC still has a say, she's a team player fr fr 🫶

  • 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
  • dirsrv_var_lib_t
/var/lib/dirsrv(/.*)?
  • 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
  • pki_common_t
/opt/nfast(/.*)?
  • pki_tomcat_cache_t
  • pki_tomcat_cert_t
/var/lib/pki-ca/alias(/.*)?
/etc/pki/pki-tomcat/ca(/.*)?
/var/lib/pki-kra/alias(/.*)?
/var/lib/pki-tks/alias(/.*)?
/etc/pki/pki-tomcat/kra(/.*)?
/var/lib/pki-ocsp/alias(/.*)?
/etc/pki/pki-tomcat/alias(/.*)?
/var/lib/ipa/pki-ca/publish(/.*)?
  • pki_tomcat_etc_rw_t
/etc/pki-ca(/.*)?
/etc/pki-kra(/.*)?
/etc/pki-tks(/.*)?
/etc/pki-ocsp(/.*)?
/etc/pki/pki-tomcat(/.*)?
/etc/sysconfig/pki/tomcat(/.*)?
  • pki_tomcat_lock_t
/run/lock/subsys/pkidaemon
  • pki_tomcat_log_t
/var/log/pki-ca(/.*)?
/var/log/pki-kra(/.*)?
/var/log/pki-tks(/.*)?
/var/log/pki-ocsp(/.*)?
/var/log/pki/pki-tomcat(/.*)?
  • pki_tomcat_tmp_t
  • pki_tomcat_var_lib_t
/var/lib/pki-ca(/.*)?
/var/lib/pki-kra(/.*)?
/var/lib/pki-tks(/.*)?
/var/lib/pki-ocsp(/.*)?
/var/lib/pki/pki-tomcat(/.*)?
  • pki_tomcat_var_run_t
/run/pki-ca.pid
/run/pki-kra.pid
/run/pki-tks.pid
/run/pki-ocsp.pid
/run/pki/tomcat(/.*)?
  • root_t
/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
/var/lib/ntp
  • user_tmp_t
/run/tlog(/.*)?
/run/user/[^/]+
/dev/shm/mono.*
/tmp/.ICE-unix(/.*)?
/tmp/.X11-unix(/.*)?
/dev/shm/pulse-shm.*
/run/user
/tmp/.X0-lock
/tmp/hsperfdata_root
/var/tmp/hsperfdata_root
/home/[^/]+/tmp
/home/[^/]+/.tmp
/run/user/[0-9]+
/tmp/gconfd-[^/]+

🧚 FILE CONTEXTS 🧚

SELinux requires files to have an extended attribute to define the file type. yes, every file needs its little label, it's an accessory and it's mandatory 💅

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

🎀 EQUIVALENCE DIRECTORIES 🎀

pki_tomcat policy stores data with multiple different file context types under the /var/lib/pki-ca 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/pki-ca /srv/pki-ca
restorecon -R -v /srv/pki-ca

pki_tomcat policy stores data with multiple different file context types under the /var/lib/pki-kra 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/pki-kra /srv/pki-kra
restorecon -R -v /srv/pki-kra

pki_tomcat policy stores data with multiple different file context types under the /var/lib/pki-ocsp 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/pki-ocsp /srv/pki-ocsp
restorecon -R -v /srv/pki-ocsp

pki_tomcat policy stores data with multiple different file context types under the /var/lib/pki-tks 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/pki-tks /srv/pki-tks
restorecon -R -v /srv/pki-tks

🌟 STANDARD FILE CONTEXT 🌟

SELinux defines the file context types for the pki_tomcat, 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 pki_tomcat_etc_rw_t
'/srv/pki_tomcat/content(/.*)?'
restorecon -R -v /srv/mypki_tomcat_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regexes! in my labeling?? it's more likely than you think 😭

The following file types are defined for pki_tomcat:

pki_tomcat_cache_t

  • Set files with the pki_tomcat_cache_t type, if you want to store the files under the /var/cache directory.

pki_tomcat_cert_t

  • Set files with the pki_tomcat_cert_t type, if you want to treat the files as pki tomcat certificate data.

Paths:

/var/lib/pki-ca/alias(/.*)?, /etc/pki/pki-tomcat/ca(/.*)?,
/var/lib/pki-kra/alias(/.*)?, /var/lib/pki-tks/alias(/.*)?,
/etc/pki/pki-tomcat/kra(/.*)?, /var/lib/pki-ocsp/alias(/.*)?,
/etc/pki/pki-tomcat/alias(/.*)?, /var/lib/ipa/pki-ca/publish(/.*)?

pki_tomcat_etc_rw_t

  • Set files with the pki_tomcat_etc_rw_t type, if you want to treat the files as pki tomcat etc read/write content.

Paths:

/etc/pki-ca(/.*)?, /etc/pki-kra(/.*)?, /etc/pki-tks(/.*)?,
/etc/pki-ocsp(/.*)?, /etc/pki/pki-tomcat(/.*)?,
/etc/sysconfig/pki/tomcat(/.*)?

pki_tomcat_exec_t

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

pki_tomcat_lock_t

  • Set files with the pki_tomcat_lock_t type, if you want to treat the files as pki tomcat lock data, stored under the /var/lock directory

pki_tomcat_log_t

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

Paths:

/var/log/pki-ca(/.*)?, /var/log/pki-kra(/.*)?, /var/log/pki-tks(/.*)?,
/var/log/pki-ocsp(/.*)?, /var/log/pki/pki-tomcat(/.*)?

pki_tomcat_tmp_t

  • Set files with the pki_tomcat_tmp_t type, if you want to store pki tomcat temporary files in the /tmp directories.

pki_tomcat_unit_file_t

  • Set files with the pki_tomcat_unit_file_t type, if you want to treat the files as pki tomcat unit content.

pki_tomcat_var_lib_t

  • Set files with the pki_tomcat_var_lib_t type, if you want to store the pki tomcat files under the /var/lib directory.

Paths:

/var/lib/pki-ca(/.*)?, /var/lib/pki-kra(/.*)?, /var/lib/pki-tks(/.*)?,
/var/lib/pki-ocsp(/.*)?, /var/lib/pki/pki-tomcat(/.*)?

pki_tomcat_var_run_t

  • Set files with the pki_tomcat_var_run_t type, if you want to store the pki tomcat files under the /run or /var/run directory.

Paths:

/run/pki-ca.pid, /run/pki-kra.pid, /run/pki-tks.pid, /run/pki-ocsp.pid,
/run/pki/tomcat(/.*)?
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 chcon = a cute little outfit for tonight, semanage fcontext = actually changing your whole wardrobe. know the difference bestie 💀👗

🌈 COMMANDS 🌈

Okay so these are the command-line besties that also know how to poke at SELinux policy stuff — same energy, different tools 💅

  • semanage fcontext — also lets you manipulate the default file context mappings. Lowkey the file-labeling hookup you need.
  • semanage permissive — also lets you manipulate whether or not a process type is permissive. Yes, that permissive.
  • semanage module — also lets you enable/disable/install/remove policy modules. All four, no cap.
  • semanage boolean — also lets you manipulate the booleans. The toggles! The lil switches!
  • system-config-selinux — a GUI tool available to customize SELinux policy settings. Mouse girlies, this one’s for you 🖱️✨

👑 AUTHOR 👑

This manual page was auto-generated using sepolicy manpage. So yeah, the robots made the page, I just gave it main character energy 😭💖

🦋 SEE ALSO 🦋

selinux(8), pki_tomcat(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8), pki_tomcat_script_selinux(8), pki_tomcat_script_selinux(8) — yes bestie, pki_tomcat_script_selinux(8) is literally there twice, and we’re keeping both because accuracy is the vibe 💅✨

This page is serving source/version pki_tomcat energy, dated 26-10-06, and living its best life as pki_tomcat_selinux(8) — byeee, go read your man pages responsibly 🫶🎀

📦 where this page comes from