stapserver_selinux(8)

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

💅 stapserver_selinux(8) — the group chat guide to SELinux policy for stapserver 🌸

okay so bestie, this is the stapserver_selinux page, section 8 of the manual, and it's literally all about the SELinux policy for stapserver processes. buckle up, it's giving secure-but-cute ✨

✨ NAME ✨

stapserver_selinux — the Security Enhanced Linux Policy for the stapserver processes, no cap 🫶

🦋 DESCRIPTION 🦋

Security-Enhanced Linux secures the stapserver processes via flexible mandatory access control. yes, mandatory, as in SELinux does not care about your vibes, it has rules 💅

The stapserver processes execute with the stapserver_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 stapserver_t

like, that's it, that's the vibe check for your process labels 👑

🎀 ENTRYPOINTS 🎀

The stapserver_t SELinux type can be entered via the stapserver_exec_t file type.

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

/usr/bin/stap-server

one path, one icon, we love a main character with a single entrance 💖

🌈 PROCESS TYPES 🌈

SELinux defines process types (domains) for each process running on the system.

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

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

The following process types are defined for stapserver:

stapserver_t
Note: semanage permissive -a stapserver_t can be used to make the process type stapserver_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated.

so permissive = it stops saying "no" but it still papers you with AVC messages, like a hall monitor who writes you up but lets you through 🫠

🔥 BOOLEANS 🔥

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

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

two out of three already on, we love a low-effort slay 💅

🧚 MANAGED FILES 🧚

The SELinux process type stapserver_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.

like, SELinux handing you the keys does NOT mean the file perms said yes, ok? both locks, every time 🔐

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

root_t

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

stapserver_log_t

/var/log/stap-server(/.*)?

stapserver_tmp_t

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

stapserver_tmpfs_t

(also no default paths listed — mystery twins 🫶)

stapserver_var_lib_t

/var/lib/stap-server(/.*)?

stapserver_var_run_t

/run/stap-server(/.*)?

🍓 FILE CONTEXTS 🍓

SELinux requires files to have an extended attribute to define the file type.

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

⭐ STANDARD FILE CONTEXT ⭐

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

yes bestie, those (/.*)? bits are regex, that's how one rule eats a whole directory tree, iconic behavior 👑

The following file types are defined for stapserver:

  • stapserver_exec_t — Set files with the stapserver_exec_t type, if you want to transition an executable to the stapserver_t domain.
  • stapserver_log_t — Set files with the stapserver_log_t type, if you want to treat the data as stapserver log data, usually stored under the /var/log directory.
  • stapserver_tmp_t — Set files with the stapserver_tmp_t type, if you want to store stapserver temporary files in the /tmp directories.
  • stapserver_tmpfs_t — Set files with the stapserver_tmpfs_t type, if you want to store stapserver files on a tmpfs file system.
  • stapserver_var_lib_t — Set files with the stapserver_var_lib_t type, if you want to store the stapserver files under the /var/lib directory.
  • stapserver_var_run_t — Set files with the stapserver_var_run_t type, if you want to store the stapserver 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.

fr fr: chcon is the temporary tattoo, semanage fcontext + restorecon is the real ink 💀

💜 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, this one's for you 🖱️✨

👑 AUTHOR 👑

This manual page was auto-generated using sepolicy manpage .

auto-generated and still ate, honestly 💅

🌸 SEE ALSO 🌸

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

and that's the whole page bestie 🫶 this one came from stapserver, dated 26-10-06, and it's sitting pretty at stapserver_selinux(8) — go forth and label responsibly 🎀💖

📦 where this page comes from