zarafa_mo...r_selinux(8)
β¨ zarafa_monitor_selinux β¨
okay bestie, so this is the SELinux policy manpage for the zarafa_monitor processes β it's from the zarafa_mo...r_selinux(8) corner of the manual-verse, and honestly? it's giving "niche but important" π
let's get into it.
πΈ NAME πΈ
zarafa_monitor_selinux β the Security Enhanced Linux Policy for the zarafa_monitor processes. literally that's the whole name, she's official π
π¦ DESCRIPTION π¦
Security-Enhanced Linux secures the zarafa_monitor processes via flexible mandatory access control. yes, mandatory β not optional, not vibes-based, mandatory π₯
The zarafa_monitor processes execute with the zarafa_monitor_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_monitor_t
run that, see what's up, you'll know immediately π
π ENTRYPOINTS π
The zarafa_monitor_t SELinux type can be entered via the zarafa_monitor_exec_t file type. that's the doorway, bestie πͺβ¨
The default entrypoint paths for the zarafa_monitor_t domain are the following:
/usr/bin/zarafa-monitor
π PROCESS TYPES π
SELinux defines process types (domains) for each process running on the system. one process, one little domain, very main-character energy π«Ά
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_monitor policy is very flexible, allowing users to set up their zarafa_monitor processes in as secure a method as possible.
The following process types are defined for zarafa_monitor:
zarafa_monitor_t
Note:semanage permissive -a zarafa_monitor_tcan be used to make the process typezarafa_monitor_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, she won't block you, but she will be watching and logging ππ
π BOOLEANS π
SELinux policy is customizable based on least access required β minimal, snatched, no extra access, obsessed. zarafa_monitor policy is extremely flexible and has several booleans that allow you to manipulate the policy and run zarafa_monitor with the tightest access possible. πβ¨
- If you want to dontaudit all daemons scheduling requests (
setsched,sys_nice), you must turn on thedaemons_dontaudit_schedulingboolean. 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 thefips_modeboolean. Enabled by default.
setsebool -P fips_mode 1
- If you want to allow system to run with NIS, you must turn on the
nis_enabledboolean. Disabled by default.
setsebool -P nis_enabled 1
- If you want to allow zarafa domains to
setrlimit/sys_resource, you must turn on thezarafa_setrlimitboolean. Disabled by default.
setsebool -P zarafa_setrlimit 1
π MANAGED FILES π
The SELinux process type zarafa_monitor_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. Note: the process's UID still needs to have DAC permissions β SELinux is not out here doing DAC's homework for it, periodt π
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_monitor_log_t
/var/log/zarafa/monitor.log.*
zarafa_monitor_var_run_t
/run/zarafa-monitor.pid
π FILE CONTEXTS π
SELinux requires files to have an extended attribute to define the file type. yeah, files have β¨labelsβ¨ now, welcome to the future.
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_monitor policy is very flexible, allowing users to set up their zarafa_monitor processes in as secure a method as possible.
β STANDARD FILE CONTEXT β
SELinux defines the file context types for the zarafa_monitor. 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. iykyk π
semanage fcontext -a -t zarafa_monitor_exec_t '/srv/zarafa_monitor/content(/.*)?'
restorecon -R -v /srv/myzarafa_monitor_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex said "I contain multitudes" π«
The following file types are defined for zarafa_monitor:
zarafa_monitor_exec_tβ Set files with thezarafa_monitor_exec_ttype if you want to transition an executable to thezarafa_monitor_tdomain.zarafa_monitor_log_tβ Set files with thezarafa_monitor_log_ttype if you want to treat the data as zarafa monitor log data, usually stored under the/var/logdirectory.zarafa_monitor_var_run_tβ Set files with thezarafa_monitor_var_run_ttype if you want to store the zarafa monitor files under the/runor/var/rundirectory.
Note: File context can be temporarily modified with thechconcommand. If you want to permanently change the file context you need to use thesemanage fcontextcommand. This will modify the SELinux labeling database. You will need to userestoreconto apply the labels. temporary vs permanent, choose wisely bestie ππ
π§ COMMANDS π§
semanage fcontextcan also be used to manipulate default file context mappings.semanage permissivecan also be used to manipulate whether or not a process type is permissive.semanage modulecan also be used to enable/disable/install/remove policy modules.semanage booleancan also be used to manipulate the booleans.system-config-selinuxis a GUI tool available to customize SELinux policy settings β yes, a GUI, for when the terminal is being too much π±οΈβ¨
πΈ AUTHOR πΈ
This manual page was auto-generated using sepolicy manpage. a bot wrote this and honestly it ate π€π
π SEE ALSO π
selinux(8), zarafa_monitor(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8)
okay that's the whole thing, you're basically an SELinux girlie now πβ¨ this page is from zarafa_monitor, dated 26-10-06, and yes it's still filed under zarafa_mo...r_selinux(8) β go forth and label responsibly, bestie π«Άπ
π¦ where this page comes from
- opensuse-leap 16.0: selinux-policy-doc 20250627+git412.dbf877ab7-160000.1.1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms