zarafa_sp...r_selinux(8)

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

✨ zarafa_spooler_selinux ✨ (that's the manual page for the SELinux policy for the zarafa_spooler processes, bestie)

Okay so like, this is the zarafa_spooler_selinux(8) man page, and it's genuinely giving security realness. Let's get into it 💅

🌸 NAME 🌸

zarafa_spooler_selinux — it's the Security Enhanced Linux Policy for the zarafa_spooler processes. Literally what it says on the tin, no cap.

🦋 DESCRIPTION 🦋

Security-Enhanced Linux secures the zarafa_spooler processes via flexible mandatory access control. Iconic. That's the whole vibe.

So the zarafa_spooler processes execute with the zarafa_spooler_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 zarafa_spooler_t

Run that and see what's up 🔥

🌈 ENTRYPOINTS 🌈

The zarafa_spooler_t SELinux type can be entered via the zarafa_spooler_exec_t file type. That's the doorway, periodt.

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

/usr/bin/zarafa-spooler

That's it. One path. She's simple like that.

👑 PROCESS TYPES 👑

SELinux defines process types (domains) for each process running on the system. It's a whole thing.

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

Policy governs the access confined processes have to files. SELinux zarafa_spooler policy is very flexible, allowing users to setup their zarafa_spooler processes in as secure a method as possible. Love that for us.

The following process types are defined for zarafa_spooler:

  • zarafa_spooler_t
Note: semanage permissive -a zarafa_spooler_t can be used to make the process type zarafa_spooler_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So like, it's not a free pass, it just means SELinux won't block stuff — but it will still snitch to the logs. 🙈

💖 BOOLEANS 💖

SELinux policy is customizable based on least access required. zarafa_spooler policy is extremely flexible and has several booleans that allow you to manipulate the policy and run zarafa_spooler with the tightest access possible. We love a configurable queen.

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

If you want to allow zarafa domains to setrlimit/sys_resource, you must turn on the zarafa_setrlimit boolean. Disabled by default.

setsebool -P zarafa_setrlimit 1

Slay. Set those booleans responsibly. 💅

🎀 MANAGED FILES 🎀

The SELinux process type zarafa_spooler_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. So like, SELinux isn't the only gatekeeper, bestie.

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

zarafa_spooler_log_t

/var/log/zarafa/spooler.log.*

zarafa_spooler_var_run_t

/run/zarafa-spooler.pid

That's a whole lot of paths but we got through it 💪

💜 FILE CONTEXTS 💜

SELinux requires files to have an extended attribute to define the file type. Very extra, but necessary.

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

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for the zarafa_spooler. 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 zarafa_spooler_exec_t '/srv/zarafa_spooler/content(/.*)?'
restorecon -R -v /srv/myzarafa_spooler_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. So like, regex is doing a lot of heavy lifting here.

The following file types are defined for zarafa_spooler:

  • zarafa_spooler_exec_t — Set files with the zarafa_spooler_exec_t type, if you want to transition an executable to the zarafa_spooler_t domain.
  • zarafa_spooler_log_t — Set files with the zarafa_spooler_log_t type, if you want to treat the data as zarafa spooler log data, usually stored under the /var/log directory.
  • zarafa_spooler_var_run_t — Set files with the zarafa_spooler_var_run_t type, if you want to store the zarafa spooler 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. So like, don't use chcon and expect it to stick around, bestie. It won't. 💀

🫶 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. For the girlies who prefer a visual interface, I see you. 🌸

🌟 AUTHOR 🌟

This manual page was auto-generated using sepolicy manpage. So like, credit to the bot that wrote it, I guess. 🤖

🌈 SEE ALSO 🌈

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

That's the whole page, bestie. Stay secure, stay slay. 💖✨

And for the cute sign-off: this was zarafa_spooler, dated 26-10-06, and the footer says zarafa_sp...r_selinux(8). Periodt. 🎀

📦 where this page comes from