git_script_selinux(8)

💅 git_script_selinux(8) — the git_script SELinux vibe check

okay bestie so this is the manual page for git_script_selinux (section 8 of the manual, if you're keeping track 🎀) — it's literally all about the SELinux policy for the git_script processes. grab a strawberry drink, we're getting into it 🍓

✨ NAME ✨

git_script_selinux — the Security Enhanced Linux Policy for the git_script processes. that's the whole name, no cap 💜

🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the git_script processes via flexible mandatory access control. that's the flex, that's the whole point, that's the moment 👑

The git_script processes execute with the git_script_t SELinux type. you can check if you've got these processes running by executing the ps command with the -Z qualifier. like this:

ps -eZ | grep git_script_t

iconic. simple. slay 🔥

🦋 ENTRYPOINTS 🦋

so the git_script_t SELinux type can be entered via the git_script_exec_t file type. that's the door, that's the entryway 🚪✨

the default entrypoint paths for the git_script_t domain are, verbatim, these:

/var/www/cgi-bin/cgit, /var/www/git/gitweb.cgi, /var/www/gitweb-
caching/gitweb.cgi

👑 PROCESS TYPES 👑

SELinux defines process types (domains) for each process running on the system. yes, every single one, it's giving main character energy for every process 🌈

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

Policy governs the access confined processes have to files. SELinux git_script policy is very flexible, allowing users to setup their git_script processes in as secure a method as possible. flexible and secure, we love a multihyphenate 💅

the following process types are defined for git_script:

git_script_t

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

🧚 BOOLEANS 🧚

SELinux policy is customizable based on least access required. git_script policy is extremely flexible and has several booleans that allow you to manipulate the policy and run git_script with the tightest access possible. tightest access possible, that's the goal, that's the dream 🎀

---

• fips_mode — 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

• git_cgi_enable_homedirs — if you want to determine whether Git CGI can search home directories, you must turn on the git_cgi_enable_homedirs boolean. Disabled by default.

setsebool -P git_cgi_enable_homedirs 1

• git_cgi_use_cifs — if you want to determine whether Git CGI can access cifs file systems, you must turn on the git_cgi_use_cifs boolean. Disabled by default.

setsebool -P git_cgi_use_cifs 1

• git_cgi_use_nfs — if you want to determine whether Git CGI can access nfs file systems, you must turn on the git_cgi_use_nfs boolean. Disabled by default.

setsebool -P git_cgi_use_nfs 1

• httpd_enable_cgi — if you want to allow httpd cgi support, you must turn on the httpd_enable_cgi boolean. Enabled by default.

setsebool -P httpd_enable_cgi 1

• nis_enabled — 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

• use_nfs_home_dirs — if you want to support NFS home directories, you must turn on the use_nfs_home_dirs boolean. Enabled by default.

setsebool -P use_nfs_home_dirs 1

• use_samba_home_dirs — if you want to support SAMBA home directories, you must turn on the use_samba_home_dirs boolean. Disabled by default.

setsebool -P use_samba_home_dirs 1

---

💖 MANAGED FILES 💖

the SELinux process type git_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 — SELinux isn't out here overriding that, bestie, both checks still happen 🙈

git_rw_content_t

/var/cache/cgit(/.*)?
/var/cache/gitweb-caching(/.*)?

git_script_tmp_t

(no default paths listed for this one — it's a mystery, it's mysterious, it's giving elusive 🦋)

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

⭐ FILE CONTEXTS ⭐

SELinux requires files to have an extended attribute to define the file type. yes, an ✨extended attribute✨, it's extra like that 💅

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 git_script policy is very flexible, allowing users to setup their git_script processes in as secure a method as possible. same energy, different section, we stay consistent 👑

🌈 STANDARD FILE CONTEXT 🌈

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

semanage fcontext -a -t git_script_exec_t
'/srv/git_script/content(/.*)?'
restorecon -R -v /srv/mygit_script_content

Note: SELinux often uses regular expressions to specify labels that match multiple files. regexes, we stan a pattern-matching queen 🧚

the following file types are defined for git_script:

git_script_exec_t

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

Paths:

/var/www/cgi-bin/cgit, /var/www/git/gitweb.cgi, /var/www/gitweb-
caching/gitweb.cgi

git_script_tmp_t

• Set files with the git_script_tmp_t type, if you want to store git script temporary files in the /tmp directories.

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 or you're gonna have a bad time 😭

🫶 COMMANDS 🫶

okay so here's the toolbelt, no gatekeeping:

• 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 visual learners, we love accessibility 💖

💀 AUTHOR 💀

this manual page was auto-generated using sepolicy manpage. yes, a robot wrote my source material, and honestly? it ate. 🤖✨

🔥 SEE ALSO 🔥

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

---

and that's the whole page, bestie 🎀 this was git_script (the manual name, right there in the footer line energy) on 26-10-06, dating back to that version stamp, and yeah — that's a wrap, periodt 💜🌸