zarafa_in...r_selinux(8)

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

💅 zarafa_in...r_selinux(8) — the SELinux Policy for zarafa_indexer, explained bestie-style

okay so real talk — this whole page is from the SELinux Policy zarafa_indexer manual, and I'm gonna walk you through it like we're texting at 2am. no gatekeeping, no cap. 🫶

✨ NAME ✨

zarafa_indexer_selinux — it's literally the Security Enhanced Linux Policy for the zarafa_indexer processes. that's the whole vibe. 💜

🌸 DESCRIPTION 🌸

Security-Enhanced Linux keeps the zarafa_indexer processes secure through flexible mandatory access control. like, it's not asking nicely, it's enforcing. 👑

The zarafa_indexer processes run with the zarafa_indexer_t SELinux type. wanna check if you've got these processes running? just run the ps command with the -Z qualifier, easy.

For example:

ps -eZ | grep zarafa_indexer_t

see? iconic. that's it, that's the check. ✨

🦋 ENTRYPOINTS 🦋

The zarafa_indexer_t SELinux type can be entered via the zarafa_indexer_exec_t file type. that's the doorway, bestie. 🚪

The default entrypoint paths for the zarafa_indexer_t domain are:

  • /usr/bin/zarafa-search
  • /usr/bin/zarafa-indexer

🎀 PROCESS TYPES 🎀

SELinux defines process types (domains) for each process running on the system. yes, every single one gets a little label. main character energy for processes, honestly. 💅

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

Policy governs the access confined processes have to files. the SELinux zarafa_indexer policy is very flexible, allowing users to set up their zarafa_indexer processes in as secure a method as possible. flexible and secure? we love a multitasker. 🌈

The following process types are defined for zarafa_indexer:

  • zarafa_indexer_t
Note: semanage permissive -a zarafa_indexer_t can be used to make the process type zarafa_indexer_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, it stops blocking but it's still gonna gossip about you in the logs. 💀

⭐ BOOLEANS ⭐

SELinux policy is customizable based on least access required. the zarafa_indexer policy is extremely flexible and has several booleans that let you manipulate the policy and run zarafa_indexer with the tightest access possible. toggles on toggles, bestie. 🎛️

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

periodt. flip the ones you need, leave the rest alone. 🙈

🔥 MANAGED FILES 🔥

The SELinux process type zarafa_indexer_t can manage files labeled with the following file types. the paths listed are the default paths for these file types. and hey — note the processes UID still need to have DAC permissions. SELinux isn't out here doing DAC's homework for it. 😭

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_indexer_log_t

/var/log/zarafa/search.log.*
/var/log/zarafa/indexer.log.*

zarafa_indexer_tmp_t

(no default paths listed for this one, it's mysterious like that 🧚)

zarafa_indexer_var_run_t

/run/zarafa-indexer
/run/zarafa-search.pid
/run/zarafa-indexer.pid

zarafa_var_lib_t

/var/lib/zarafa(/.*)?
/var/lib/zarafa-webapp(/.*)?
/var/lib/zarafa-webaccess(/.*)?

🍓 FILE CONTEXTS 🍓

SELinux requires files to have an extended attribute to define the file type. yes, files have vibes and the vibes are stored in attributes. 💅

You can see the context of a file using the -Z option to ls.

Policy governs the access confined processes have to these files. the SELinux zarafa_indexer policy is very flexible, allowing users to set up their zarafa_indexer processes in as secure a method as possible. (yes we said this twice, it's that important, okay 😤)

STANDARD FILE CONTEXT

SELinux defines the file context types for zarafa_indexer. 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. like so:

semanage fcontext -a -t zarafa_indexer_exec_t '/srv/zarafa_indexer/content(/.*)?'
restorecon -R -v /srv/myzarafa_indexer_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies rise. 🧚

The following file types are defined for zarafa_indexer:

zarafa_indexer_exec_t

  • Set files with the zarafa_indexer_exec_t type if you want to transition an executable to the zarafa_indexer_t domain.

Paths:

/usr/bin/zarafa-search, /usr/bin/zarafa-indexer

zarafa_indexer_log_t

  • Set files with the zarafa_indexer_log_t type if you want to treat the data as zarafa indexer log data, usually stored under the /var/log directory.

Paths:

/var/log/zarafa/search.log.*, /var/log/zarafa/indexer.log.*

zarafa_indexer_tmp_t

  • Set files with the zarafa_indexer_tmp_t type if you want to store zarafa indexer temporary files in the /tmp directories.

zarafa_indexer_var_run_t

  • Set files with the zarafa_indexer_var_run_t type if you want to store the zarafa indexer files under the /run or /var/run directory.

Paths:

/run/zarafa-indexer, /run/zarafa-search.pid, /run/zarafa-indexer.pid
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. a whole GUI, for the girlies who like clicking. 🖱️✨

🧚 AUTHOR 🧚

This manual page was auto-generated using sepolicy manpage. a bot wrote this and honestly? it ate. 💅

👑 SEE ALSO 👑

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

that's the whole page bestie, you're officially an SELinux scholar now 🎓💖

sign-off era: this gem comes from zarafa_indexer, dated 26-10-06, and it lives under the manual name zarafa_in...r_selinux(8). can't believe the filename got cut off mid-word like that, it's giving "texting while walking" energy 😭 go forth and restorecon responsibly! 🦋🎀💜

📦 where this page comes from