uux_selinux(8)

💅 uux_selinux — the SELinux glow-up for uux processes ✨

okay bestie, so this is the manual page for uux_selinux — the SELinux policy that keeps an eye on the uux processes. it's part of the SELinux Policy uux situation, and honestly? it's giving secure. let's get into it 🫶

---

✨ NAME ✨

uux_selinux — Security Enhanced Linux Policy for the uux processes. that's the whole vibe. no cap.

---

🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the uux processes via flexible mandatory access control. like, it's literally the bodyguard for your uux processes, and it takes the job very seriously 💅.

the uux processes execute with the uux_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 uux_t

go ahead and run that, bestie. it's a vibe check for your processes 👑

---

🚪 ENTRYPOINTS 🚪

the uux_t SELinux type can be entered via the uux_exec_t file type. so that's the door you walk through to get into the uux_t domain.

the default entrypoint paths for the uux_t domain are the following:

/usr/bin/uux

that's it. that's the spot. iconic ✨

---

👑 PROCESS TYPES 👑

SELinux defines process types (domains) for each process running on the system. think of it like each process gets its own little assigned seat in the SELinux cafeteria.

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

policy governs the access confined processes have to files. SELinux uux policy is very flexible allowing users to setup their uux processes in as secure a method as possible. we love flexibility that doesn't compromise safety, periodt 💖.

the following process types are defined for uux:

uux_t

note: semanage permissive -a uux_t can be used to make the process type uux_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so it's like, still snitching, just not blocking. iykyk 🕵️‍♀️

---

🎛️ BOOLEANS 🎛️

SELinux policy is customizable based on least access required. uux policy is extremely flexible and has several booleans that allow you to manipulate the policy and run uux with the tightest access possible. tightest access = main character energy.

if you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean. enabled by default. so it's already on, but here's how you'd do it if you ever need to:

setsebool -P fips_mode 1

if you want to allow system to run with NIS, you must turn on the nis_enabled boolean. disabled by default. so you'd need to flip it on:

setsebool -P nis_enabled 1

that's the whole booleans section. short and sweet, just like a good group chat message 💬

---

📂 MANAGED FILES 📂

the SELinux process type uux_t can manage files labeled with the following file types. the paths listed are the default paths for these file types. but bestie, note the processes UID still need to have DAC permissions. SELinux isn't out here overriding the basics, it's just adding a whole extra layer of security 🛡️.

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

uucpd_spool_t

/var/spool/uucp(/.*)?
/var/spool/uucppublic(/.*)?

those are the paths. memorize them or don't, but they're here for you 🫶

---

🏷️ FILE CONTEXTS 🏷️

SELinux requires files to have an extended attribute to define the file type. it's like a little name tag for every file, but invisible. spooky? no, secure.

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 uux policy is very flexible allowing users to setup their uux processes in as secure a method as possible. yes, they said it again, because it's that important 💅.

🌈 STANDARD FILE CONTEXT 🌈

SELinux defines the file context types for the uux. 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 uux_exec_t '/srv/uux/content(/.*)?'
restorecon -R -v /srv/myuux_content

note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies, this one's for you 🧚

the following file types are defined for uux:

uux_exec_t

• set files with the uux_exec_t type, if you want to transition an executable to the uux_t domain.

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 chcon is like a temporary tattoo, semanage fcontext + restorecon is the real ink. choose wisely 🎀

---

🛠️ 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.

that's the toolkit, bestie. go forth and configure ✨

---

✍️ AUTHOR ✍️

this manual page was auto-generated using sepolicy manpage. so no human wrote this originally, but i'm here to make it make sense for you 💖

---

👀 SEE ALSO 👀

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

that's the whole friend group. they all hang out together 🫶

---

and that's the tea, bestie. this page was generated for uux on 26-10-06, and it's officially the uux_selinux(8) manual — go be secure and slay 💅✨