zarafa_de...r_selinux(8)

πŸ“¦
version 20250627+git412.dbf877ab7 Β· 7 versions
, in opensuse-leap 16.0

okay bestie, welcome to the zarafa_deliver_selinux(8) manual β€” the zarafa_de...r_selinux(8) page in the header, and the SELinux Policy zarafa_deliver one. it's giving security documentation but make it make sense. πŸ«ΆπŸ’…


🌸 NAME 🌸

zarafa_deliver_selinux β€” the Security Enhanced Linux Policy for the zarafa_deliver processes. literally the whole vibe of this page. ✨

πŸ›‘οΈ DESCRIPTION πŸ›‘οΈ

Security-Enhanced Linux secures the zarafa_deliver processes via flexible mandatory access control. no cap, that's the whole point.

The zarafa_deliver processes execute with the zarafa_deliver_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier. bestie, it's a vibe check for your processes.

For example:

ps -eZ | grep zarafa_deliver_t

πŸšͺ ENTRYPOINTS πŸšͺ

The zarafa_deliver_t SELinux type can be entered via the zarafa_deliver_exec_t file type. that's the doorway, iykyk.

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

/usr/bin/zarafa-dagent

🧠 PROCESS TYPES 🧠

SELinux defines process types (domains) for each process running on the system. yes, every process gets its own little domain era.

You can see the context of a process using the -Z option to ps. iconic flag, honestly.

Policy governs the access confined processes have to files. SELinux zarafa_deliver policy is very flexible allowing users to setup their zarafa_deliver processes in as secure a method as possible.

The following process types are defined for zarafa_deliver:

  • zarafa_deliver_t
Note: semanage permissive -a zarafa_deliver_t can be used to make the process type zarafa_deliver_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, it's chill but it's still logging. πŸ’€

πŸŽ›οΈ BOOLEANS πŸŽ›οΈ

SELinux policy is customizable based on least access required. zarafa_deliver policy is extremely flexible and has several booleans that allow you to manipulate the policy and run zarafa_deliver with the tightest access possible. booleans are basically the little switches of the SELinux world, and we love a customizable queen. πŸ‘‘

  • daemons_dontaudit_scheduling β€” if you want to dontaudit all daemons scheduling requests (setsched, sys_nice), you must turn on the daemons_dontaudit_scheduling boolean. it's enabled by default. run: setsebool -P daemons_dontaudit_scheduling 1
  • fips_mode β€” if you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean. it's enabled by default. run: setsebool -P fips_mode 1
  • nis_enabled β€” if you want to allow system to run with NIS, you must turn on the nis_enabled boolean. it's disabled by default. run: setsebool -P nis_enabled 1
  • zarafa_setrlimit β€” if you want to allow zarafa domains to setrlimit/sys_resource, you must turn on the zarafa_setrlimit boolean. it's disabled by default. run: setsebool -P zarafa_setrlimit 1

πŸ“ MANAGED FILES πŸ“

The SELinux process type zarafa_deliver_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 needs to have DAC permissions, so don't forget that part.

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_deliver_log_t

/var/log/zarafa/dagent.log.*

zarafa_deliver_tmp_t

no default paths listed here.

zarafa_deliver_var_run_t

/run/zarafa-dagent.pid

🏷️ FILE CONTEXTS 🏷️

SELinux requires files to have an extended attribute to define the file type. it's giving extra metadata energy, and honestly? slay.

You can see the context of a file using the -Z option to ls. yes, the same -Z family as before, consistency queen.

Policy governs the access confined processes have to these files. SELinux zarafa_deliver policy is very flexible allowing users to setup their zarafa_deliver processes in as secure a method as possible.

🌼 STANDARD FILE CONTEXT 🌼

SELinux defines the file context types for the zarafa_deliver. 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. bestie, we're relabeling. carefully. πŸŽ€

semanage fcontext -a -t zarafa_deliver_exec_t '/srv/zarafa_deliver/content(/.*)?'
restorecon -R -v /srv/myzarafa_deliver_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex stays winning, unfortunately. 😭

The following file types are defined for zarafa_deliver:

  • zarafa_deliver_exec_t β€” set files with the zarafa_deliver_exec_t type, if you want to transition an executable to the zarafa_deliver_t domain.
  • zarafa_deliver_log_t β€” set files with the zarafa_deliver_log_t type, if you want to treat the data as zarafa deliver log data, usually stored under the /var/log directory.
  • zarafa_deliver_tmp_t β€” set files with the zarafa_deliver_tmp_t type, if you want to store zarafa deliver temporary files in the /tmp directories.
  • zarafa_deliver_var_run_t β€” set files with the zarafa_deliver_var_run_t type, if you want to store the zarafa deliver 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. temporary vs permanent is literally the plot of every SELinux story. πŸ’…

πŸ› οΈ 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.

πŸ‘‘ AUTHOR πŸ‘‘

This manual page was auto-generated using sepolicy manpage .

πŸ¦‹ SEE ALSO πŸ¦‹


πŸ’– and that's the whole page, bestie! this one is from the zarafa_deliver source/version, dated 26-10-06, and it's the zarafa_de...r_selinux(8) manual. go off and keep those labels cute. πŸ’…βœ¨

πŸ“¦ where this page comes from