piranha_pulse_selinux(8)

📦 version 38.1.87, in centos-stream 9

✨ piranha_pulse_selinux — the manual page, but make it slay ✨

Okay bestie, so this is the manual page for piranha_pulse_selinux (like, from the SELinux Policy piranha_pulse collection, iykyk). It's giving security, it's giving mandatory access control, and honestly? It's kind of iconic. Let me break it down for you. 🫶

💖 NAME 💖

piranha_pulse_selinux — the Security Enhanced Linux Policy for all the piranha_pulse processes, fr fr. No cap.

🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the piranha_pulse processes via flexible mandatory access control. Lowkey powerful stuff.

So here's the tea: the piranha_pulse processes execute with the piranha_pulse_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 piranha_pulse_t

That's it, that's the vibe check. 💅

🎀 ENTRYPOINTS 🎀

The piranha_pulse_t SELinux type can be entered via the piranha_pulse_exec_t file type. So that's the door, basically.

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

/usr/sbin/pulse

🦋 PROCESS TYPES 🦋

SELinux defines process types (domains) for each process running on the system. Every process gets its own little main character energy, periodt.

You can see the context of a process using the -Z option to ps. Very demure, very mindful.

Policy governs the access confined processes have to files. The SELinux piranha_pulse policy is very flexible, allowing users to setup their piranha_pulse processes in as secure a method as possible. Obsessed with the flexibility tbh.

The following process types are defined for piranha_pulse:

  • piranha_pulse_t
💡 Note: semanage permissive -a piranha_pulse_t can be used to make the process type piranha_pulse_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So like, it's chill mode but SELinux is still watching 👀.

⭐ BOOLEANS ⭐

SELinux policy is customizable based on least access required. The piranha_pulse policy is extremely flexible and has several booleans that allow you to manipulate the policy and run piranha_pulse with the tightest access possible. Tightest access = bestie access, ngl.

  • 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 piranha_pulse_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 said "you still gotta have your own permissions, bestie, I'm not doing everything for you.")

💜 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

/var/run/crm(/.*)?
/var/run/cman_.*
/var/run/rsctmp(/.*)?
/var/run/aisexec.*
/var/run/heartbeat(/.*)?
/var/run/pcsd-ruby.socket
/var/run/corosync-qnetd(/.*)?
/var/run/corosync-qdevice(/.*)?
/var/run/pcsd.socket
/var/run/corosync.pid
/var/run/cpglockd.pid
/var/run/rgmanager.pid
/var/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

💜 piranha_pulse_var_run_t

/var/run/pulse.pid

💜 piranha_tmpfs

(no default paths listed — it's mysterious like that 🙈)

💜 root_t

/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd

💜 systemd_passwd_var_run_t

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

🧚 FILE CONTEXTS 🧚

SELinux requires files to have an extended attribute to define the file type. Every file needs its little label, okay? It's called fashion.

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 piranha_pulse policy is very flexible, allowing users to setup their piranha_pulse processes in as secure a method as possible. Again. Because flexibility is the moment.

🌸 STANDARD FILE CONTEXT 🌸

SELinux defines the file context types for piranha_pulse. 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. Like so:

semanage fcontext -a -t piranha_pulse_var_run_t '/srv/mypiranha_pulse_content(/.*)?'
restorecon -R -v /srv/mypiranha_pulse_content
💡 Note: SELinux often uses regular expressions to specify labels that match multiple files. Regex girlies, rise 🫶

The following file types are defined for piranha_pulse:

💅 piranha_pulse_exec_t

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

💅 piranha_pulse_initrc_exec_t

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

💅 piranha_pulse_tmpfs_t

  • Set files with the piranha_pulse_tmpfs_t type, if you want to store piranha pulse files on a tmpfs file system.

💅 piranha_pulse_var_run_t

  • Set files with the piranha_pulse_var_run_t type, if you want to store the piranha pulse 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. Temp changes are cute but they don't last, bestie. Make it permanent.

🔥 COMMANDS 🔥

  • semanage fcontext can also be used to manipulate default file context mappings. The icon.
  • semanage permissive can also be used to manipulate whether or not a process type is permissive. Periodt.
  • semanage module can also be used to enable/disable/install/remove policy modules. So many slashes, so much power.
  • semanage boolean can also be used to manipulate the booleans. Boolean baddies unite.
  • system-config-selinux is a GUI tool available to customize SELinux policy settings. For when you want to point and click instead of type. No judgment 🎀

👑 AUTHOR 👑

This manual page was auto-generated using sepolicy manpage. Not me being a bot-written icon 💀✨

🌟 SEE ALSO 🌟

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

And that's the whole page, bestie! This beauty is from the piranha_pulse manual, dated 26-10-23, and it's the piranha_pulse_selinux(8) page. Go forth and be secure 💖🦋🌸

📦 where this page comes from