qmail_start_selinux(8)

💅 qmail_start_selinux — the manual page, but make it make sense

okay bestie, so this is the qmail_start_selinux(8) page, and it's literally all about the Security Enhanced Linux Policy for the qmail_start processes. yes, that's the whole vibe. SELinux, but make it qmail. let's go ✨

---

🎀 NAME

qmail_start_selinux — Security Enhanced Linux Policy for the qmail_start processes. that's it, that's the name. periodt.

---

🌸 DESCRIPTION

Security-Enhanced Linux secures the qmail_start processes via flexible mandatory access control. like, it's giving strict-but-fair parent energy 🔥

The qmail_start processes execute with the qmail_start_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 qmail_start_t

go ahead, run it, do a little vibe check on your processes 💅

---

🦋 ENTRYPOINTS

The qmail_start_t SELinux type can be entered via the qmail_start_exec_t file type.

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

/var/qmail/bin/qmail-start

that's the one door in, bestie 🚪✨

---

👑 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 qmail_start policy is very flexible, allowing users to setup their qmail_start processes in as secure a method as possible. highkey a glow-up for your security posture 💖

The following process types are defined for qmail_start:

qmail_start_t

Note: semanage permissive -a qmail_start_t can be used to make the process type qmail_start_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so it's chill about blocking you but it's still gonna talk about it behind your back 😭

---

🌈 BOOLEANS

SELinux policy is customizable based on least access required. qmail_start policy is extremely flexible and has several booleans that allow you to manipulate the policy and run qmail_start with the tightest access possible. toggles, but make it secure 🎛️

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 already on by default, so like… you're kind of already slaying 🫶

---

💜 MANAGED FILES

The SELinux process type qmail_start_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. don't forget the classic perms, bestie, SELinux isn't 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

/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

• root_t

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

look at all those paths, it's a whole aesthetic 🎀

---

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

⭐ STANDARD FILE CONTEXT

SELinux defines the file context types for the qmail_start; 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 qmail_start_exec_t '/srv/qmail_start/content(/.*)?'
restorecon -R -v /srv/myqmail_start_content

Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies rise 🙌

The following file types are defined for qmail_start:

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

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 bestie 💅

---

🧚 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 when the terminal is doing too much 😌

---

💀 AUTHOR

This manual page was auto-generated using sepolicy manpage . not me being a bot-authored icon 🤖✨

---

🔥 SEE ALSO

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

go read those too, iykyk 🫶

---

okay that's the whole page!! this beauty is from qmail_start, dated 26-10-06, and it lives under qmail_start_selinux(8) — mwah, go forth and label responsibly 💖🎀✨