nvme_stas_selinux(8)

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

💅 NAME 💅

nvme_stas_selinux — Security Enhanced Linux Policy for the nvme_stas processes

Welcome to the nvme_stas_selinux(8) glow-up, bestie. This is the SELinux policy page for nvme_stas, and yes, it's giving very “security girlie” energy. 🎀

✨ DESCRIPTION ✨

Security-Enhanced Linux secures the nvme_stas processes via flexible mandatory access control. Lowkey iconic of SELinux, honestly. 💅

The nvme_stas processes execute with the nvme_stas_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 nvme_stas_t

See? Very demure, very mindful. 🦋

🚪 ENTRYPOINTS 🚪

The nvme_stas_t SELinux type can be entered via the nvme_stas_exec_t file type.

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

  • /usr/bin/stacd
  • /usr/bin/stafd

These are the main-character doors into the nvme_stas_t domain, periodt. 👑

🧚 PROCESS TYPES 🧚

SELinux defines process types (domains) for each process running on the system. It’s a whole labeling situation, and honestly it ate.

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

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

The following process types are defined for nvme_stas:

  • nvme_stas_t
Note: semanage permissive -a nvme_stas_t can be used to make the process type nvme_stas_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So like… permissive is not a free pass, bestie. 🫶

🎚️ BOOLEANS 🎚️

SELinux policy is customizable based on least access required. nvme_stas policy is extremely flexible and has several booleans that allow you to manipulate the policy and run nvme_stas with the tightest access possible. Very “lock the door but make it cute” vibes. 🔐

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

Both enabled by default, both slaying in their own quiet way. ✨

📂 MANAGED FILES 📂

The SELinux process type nvme_stas_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. Important little caveat, don't skip it. 🌸

  • cluster_conf_t — default paths:
    • /etc/cluster(/.*)?
  • cluster_var_lib_t — default paths:
    • /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 — default paths:
    • /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
  • nvme_stas_tmpfs_t — no default paths listed here 🫶
  • nvme_stas_var_run_t — default paths:
    • /run/stacd(/.*)?
    • /run/stafd(/.*)?
  • root_t — default paths:
    • /sysroot/.aleph-version.json
    • /sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
    • /
    • /initrd
    • /var/lib/ntp
  • systemd_passwd_var_run_t — default paths:
    • /run/systemd/ask-password(/.*)?
    • /run/systemd/ask-password-block(/.*)?
  • udev_var_run_t — default paths:
    • /run/udev(/.*)?
    • /dev/.udev(/.*)?
    • /run/libgpod(/.*)?
    • /run/PackageKit/udev(/.*)?
    • /dev/.udevdb
    • /dev/udev.tbl

That’s a whole lot of paths, but we keep every single one because bestie does not do missing lore. 🍓

🏷️ FILE CONTEXTS 🏷️

SELinux requires files to have an extended attribute to define the file type. It’s giving “files have vibes too.” ✨

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

🎀 STANDARD FILE CONTEXT 🎀

SELinux defines the file context types for the nvme_stas. 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 nvme_stas_exec_t '/srv/nvme_stas/content(/.*)?'
restorecon -R -v /srv/mynvme_stas_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. Regex girlies stay winning. 💅

The following file types are defined for nvme_stas:

  • nvme_stas_cache_t — Set files with the nvme_stas_cache_t type, if you want to store the files under the /var/cache directory.
    • Paths:
      • /var/cache/stacd(/.*)?
      • /var/cache/stafd(/.*)?
  • nvme_stas_exec_t — Set files with the nvme_stas_exec_t type, if you want to transition an executable to the nvme_stas_t domain.
    • Paths:
      • /usr/bin/stacd
      • /usr/bin/stafd
  • nvme_stas_tmpfs_t — Set files with the nvme_stas_tmpfs_t type, if you want to store nvme stas files on a tmpfs file system.
  • nvme_stas_unit_file_t — Set files with the nvme_stas_unit_file_t type, if you want to treat the files as nvme stas unit content.
    • Paths:
      • /usr/lib/systemd/system/stacd.service
      • /usr/lib/systemd/system/stafd.service
      • /usr/lib/systemd/system/stas-config.target
      • /usr/lib/systemd/system/stas-config@.service
  • nvme_stas_var_run_t — Set files with the nvme_stas_var_run_t type, if you want to store the nvme stas files under the /run or /var/run directory.
    • Paths:
      • /run/stacd(/.*)?
      • /run/stafd(/.*)?
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 is a whole character arc, okay? 😭

🛠️ 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.

A lil command cheat sheet, but make it fashion. 💜

👑 AUTHOR 👑

This manual page was auto-generated using sepolicy manpage .

Auto-generated and still serving looks. 💅

🌈 SEE ALSO 🌈

Read the whole friend group, iykyk. 🦋

And that's the whole page, bestie. This glow-up came from nvme_stas, dated 26-10-06, and yes it’s still nvme_stas_selinux(8) at the bottom because the footer said so. Mwah. 💖

📦 where this page comes from