cvs_script_selinux(8)

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

πŸ’… cvs_script_selinux β€” the SELinux glow-up for cvs_script processes πŸ’…

Okay bestie, so this is the manual page for cvs_script_selinux(8) β€” it's literally the Security Enhanced Linux Policy for the cvs_script processes. No cap, it's giving secure vibes only. Let's break it down so you can slay your SELinux game. πŸŽ€


✨ NAME ✨

cvs_script_selinux β€” Security Enhanced Linux Policy for the cvs_script processes. Periodt. πŸ’–


πŸ¦‹ DESCRIPTION πŸ¦‹

So like, Security-Enhanced Linux secures the cvs_script processes via flexible mandatory access control. It's basically the bodyguard for your processes, okay? 🫢

The cvs_script processes execute with the cvs_script_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier. Like, just run this and you'll see:

ps -eZ | grep cvs_script_t

Easy peasy, lemon squeezy. πŸ‹


🌸 ENTRYPOINTS 🌸

The cvs_script_t SELinux type can be entered via the cvs_script_exec_t file type. So if you see that type, it's like the VIP pass into the cvs_script_t domain. πŸ’…

The default entrypoint paths for the cvs_script_t domain are the following β€” memorize these, bestie:

  • /var/www/cgi-bin/cvsweb.cgi
  • /usr/share/cvsweb/cvsweb.cgi

πŸ”₯ PROCESS TYPES πŸ”₯

SELinux defines process types (domains) for each process running on the system. It's like each process gets its own little label, and honestly? Iconic. πŸ‘‘

You can see the context of a process using the -Z option to ps. Just add that -Z and you're in the know. ✨

Policy governs the access confined processes have to files. The SELinux cvs_script policy is very flexible, allowing users to set up their cvs_script processes in as secure a method as possible. Like, it's highkey flexible but still keeps things locked down. πŸ”’

The following process types are defined for cvs_script:

  • cvs_script_t
Note: semanage permissive -a cvs_script_t can be used to make the process type cvs_script_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So like, it's permissive but it still tattles. Not me being a snitch. 😭

πŸ’– BOOLEANS πŸ’–

SELinux policy is customizable based on least access required. The cvs_script policy is extremely flexible and has several booleans that allow you to manipulate the policy and run cvs_script with the tightest access possible. Booleans are like little toggles, and you can flip them to match your vibe. 🎚️

If you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean. Enabled by default. So just run:

setsebool -P fips_mode 1

If you want to allow httpd cgi support, you must turn on the httpd_enable_cgi boolean. Enabled by default. Run:

setsebool -P httpd_enable_cgi 1

If you want to allow system to run with NIS, you must turn on the nis_enabled boolean. Disabled by default. So if you need it, flip it like:

setsebool -P nis_enabled 1

🌈 MANAGED FILES 🌈

The SELinux process type cvs_script_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. Like, SELinux can't override DAC, bestie. It's a team effort. 🀝

  • cvs_rw_content_t
  • cvs_tmp_t

πŸŽ€ FILE CONTEXTS πŸŽ€

SELinux requires files to have an extended attribute to define the file type. It's like a little name tag for your files. 🏷️

You can see the context of a file using the -Z option to ls. Just add -Z and you'll see all the tea. β˜•

Policy governs the access confined processes have to these files. The SELinux cvs_script policy is very flexible, allowing users to set up their cvs_script processes in as secure a method as possible. We love a flexible queen. πŸ‘‘

STANDARD FILE CONTEXT

SELinux defines the file context types for cvs_script. 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 this:

semanage fcontext -a -t cvs_script_exec_t '/srv/cvs_script/content(/.*)?'
restorecon -R -v /srv/mycvs_script_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. Regex is giving main character energy, honestly. πŸ”₯

The following file types are defined for cvs_script:

  • cvs_script_exec_t β€” Set files with the cvs_script_exec_t type if you want to transition an executable to the cvs_script_t domain. Paths:
    • /var/www/cgi-bin/cvsweb.cgi
    • /usr/share/cvsweb/cvsweb.cgi
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, chcon is a quick fix, but semanage fcontext + restorecon is the forever vibe. πŸ’

🧚 COMMANDS 🧚

Here are the tools you can use to manipulate all this SELinux goodness:

  • 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. Slay, automation. πŸ€–βœ¨


🌟 SEE ALSO 🌟


And that's the whole vibe, bestie. This page was brought to you by cvs_script on 26-10-06 β€” like, the manual page for cvs_script_selinux(8) is literally right here. Go forth and SELinux responsibly. πŸ’œπŸ¦‹

πŸ“¦ where this page comes from