qmail_remote_selinux(8)

✨ qmail_remote_selinux ✨

Hey bestie! This is the manual page for qmail_remote_selinux — the SELinux policy that keeps the qmail_remote processes safe and sound. Come learn with me, it's giving secure 💅

(This page is from qmail_remote_selinux(8), part of the SELinux Policy for qmail_remote — okay let's dive in!)

---

🎀 NAME 🎀

qmail_remote_selinux — the Security Enhanced Linux Policy for the qmail_remote processes. That's it, that's the vibe. No cap.

---

🌸 DESCRIPTION 🌸

Security-Enhanced Linux (that's SELinux to its friends) secures the qmail_remote processes via flexible mandatory access control. Basically it's the bodyguard that decides who gets to talk to what, and it does it so well.

The qmail_remote processes execute with the qmail_remote_t SELinux type. Wanna check if you've got these processes running? Just run the ps command with the -Z qualifier, easy peasy.

For example:

ps -eZ | grep qmail_remote_t

Go ahead, try it, it's iconic ✨

---

🦋 ENTRYPOINTS 🦋

The qmail_remote_t SELinux type can be entered via the qmail_remote_exec_t file type. Entrypoint era!

The default entrypoint paths for the qmail_remote_t domain are literally:

/var/qmail/bin/qmail-remote

That's the one, that's the door 🚪✨

---

💖 PROCESS TYPES 💖

SELinux defines process types (also known as domains, iykyk) for each process running on the system.

You can see the context of a process using the -Z option to ps — go take a peek bestie.

Policy governs the access confined processes have to files. The SELinux qmail_remote policy is super flexible, allowing users to set up their qmail_remote processes in as secure a method as possible. Tight security AND flexibility? Obsessed.

The following process types are defined for qmail_remote:

• qmail_remote_t

Note: semanage permissive -a qmail_remote_t can be used to make the process type qmail_remote_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So like, it's still tattling on you, just not stopping you 🙈

---

🌈 BOOLEANS 🌈

SELinux policy is customizable based on least access required — the philosophy of "she just needs enough and nothing more", periodt.

The qmail_remote policy is extremely flexible and has several booleans that allow you to manipulate the policy and run qmail_remote with the tightest access possible. Get into it.

If you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean. Enabled by default — she's already on, bestie.

setsebool -P fips_mode 1

---

🎀 MANAGED FILES 🎀

The SELinux process type qmail_remote_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. Just remember, the processes UID still need to have DAC permissions — SELinux can't do everything.

• qmail_spool_t

/var/qmail/queue(/.*)?

That's where the magic lives 💅

---

💜 FILE CONTEXTS 💜

SELinux requires files to have an extended attribute to define the file type. It's a whole labeling system, very orderly, very organized.

You can see the context of a file using the -Z option to ls — check it out.

Policy governs the access confined processes have to these files. The SELinux qmail_remote policy is very flexible, allowing users to set up their qmail_remote processes in as secure a method as possible. Yeah, I said it twice, because it's true and worth repeating.

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for qmail_remote. 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. It's a two-step slay.

semanage fcontext -a -t qmail_remote_exec_t '/srv/qmail_remote/content(/.*)?'
restorecon -R -v /srv/myqmail_remote_content

Note: SELinux often uses regular expressions to specify labels that match multiple files. Regex bestie, she's everywhere.

The following file types are defined for qmail_remote:

• qmail_remote_exec_t — Set files with the qmail_remote_exec_t type if you want to transition an executable to the qmail_remote_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. So don't think chcon is permanent, because she is NOT 💀

---

🔥 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 whole GUI, fancy 👑

---

🌟 AUTHOR 🌟

This manual page was auto-generated using sepolicy manpage. Not me writing it by hand, the machine did it, and honestly? She ate. 💅

---

🫶 SEE ALSO 🫶

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

Go read those too if you want the full lore, bestie ✨

---

And that's the whole page, bestie! 🎀 You're now fully educated on the qmail_remote_selinux policy — go forth and be secure. This cutie of a page was from qmail_remote dated 26-10-06, and it's the qmail_remote_selinux(8) manual, mwah 💋