svnserve_selinux(8)

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

πŸ’– svnserve_selinux β€” the manual, but make it make sense πŸ’–

okay so bestie, welcome to the svnserve_selinux(8) era πŸ’… this is the SELinux Policy for the svnserve processes page, and we're gonna get you comfy with it. no cap, it's giving "niche but important" and honestly? iconic.


✨ NAME ✨

svnserve_selinux β€” Security Enhanced Linux Policy for the svnserve processes πŸŽ€


🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the svnserve processes via flexible mandatory access control. lowkey the whole point is that SELinux is the bodyguard and svnserve is the celeb πŸ’…

The svnserve processes execute with the svnserve_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 svnserve_t

go off, ps 🫢


πŸ¦‹ ENTRYPOINTS πŸ¦‹

The svnserve_t SELinux type can be entered via the svnserve_exec_t file type.

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

/usr/bin/svnserve

that's the one path, periodt 🌟


πŸ‘‘ PROCESS TYPES πŸ‘‘

SELinux defines process types (domains) for each process running on the system.

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

Policy governs the access confined processes have to files. SELinux svnserve policy is very flexible allowing users to setup their svnserve processes in as secure a method as possible. it's literally so accommodating ✨

The following process types are defined for svnserve:

svnserve_t
Note: semanage permissive -a svnserve_t can be used to make the process type svnserve_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 watching you πŸ‘€

πŸŽ€ BOOLEANS πŸŽ€

SELinux policy is customizable based on least access required. svnserve policy is extremely flexible and has several booleans that allow you to manipulate the policy and run svnserve with the tightest access possible. we love a modular 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 confined applications to run with kerberos, you must turn on the kerberos_enabled boolean. Enabled by default.
setsebool -P kerberos_enabled 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

see how easy that was? slay πŸ’…


🌈 MANAGED FILES 🌈

The SELinux process type svnserve_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. okay so this is the big list, stay with me 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
  • security_t
/selinux
  • svnserve_content_t
/var/svn(/.*)?
/var/subversion/repo(/.*)?
/var/lib/subversion/repo(/.*)?
  • svnserve_log_t
/var/log/svnserve(/.*)?
  • svnserve_tmp_t β€” no default paths listed, it's a mystery but she's valid πŸ’€
  • svnserve_var_run_t
/run/svnserve.pid
/run/svnserve(/.*)?

look at all those paths, we ate πŸ“


🧚 FILE CONTEXTS 🧚

SELinux requires files to have an extended attribute to define the file type.

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 svnserve policy is very flexible allowing users to setup their svnserve processes in as secure a method as possible. yes we're saying it again, because it's true πŸ’–

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for the svnserve, 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 svnserve_exec_t '/srv/svnserve/content(/.*)?'
restorecon -R -v /srv/mysvnserve_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies rise πŸ™ˆ

The following file types are defined for svnserve:

🌟 svnserve_content_t

  • Set files with the svnserve_content_t type, if you want to treat the files as svnserve content.

Paths:

/var/svn(/.*)?, /var/subversion/repo(/.*)?,
/var/lib/subversion/repo(/.*)?

🌟 svnserve_exec_t

  • Set files with the svnserve_exec_t type, if you want to transition an executable to the svnserve_t domain.

🌟 svnserve_initrc_exec_t

  • Set files with the svnserve_initrc_exec_t type, if you want to transition an executable to the svnserve_initrc_t domain.

🌟 svnserve_log_t

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

🌟 svnserve_tmp_t

  • Set files with the svnserve_tmp_t type, if you want to store svnserve temporary files in the /tmp directories.

🌟 svnserve_unit_file_t

  • Set files with the svnserve_unit_file_t type, if you want to treat the files as svnserve unit content.

Paths:

/lib/systemd/system/svnserve.service,
/usr/lib/systemd/system/svnserve.service

🌟 svnserve_var_run_t

  • Set files with the svnserve_var_run_t type, if you want to store the svnserve files under the /run or /var/run directory.

Paths:

/run/svnserve.pid, /run/svnserve(/.*)?
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.

so many tools, so many vibes πŸ› οΈβœ¨


πŸŽ€ AUTHOR πŸŽ€

This manual page was auto-generated using sepolicy manpage . β€” yes she was born from a script and she's still serving πŸ‘‘


πŸ”₯ SEE ALSO πŸ”₯

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

go read those too, iykyk 🫢


and that's the whole page, bestie! this was svnserve from 26-10-06 (that's the date, not a vibe β€” well, also a vibe) and it's the svnserve_selinux(8) manual, auto-generated and now fully translated into group-chat. mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from