cinder_backup_selinux(8)

💅 cinder_backup_selinux — the glow-up guide 💅

okay bestie, so this is the Security Enhanced Linux Policy for the cinder_backup processes, and honestly? It's giving main character energy in the SELinux world. This is the cinder_backup_selinux(8) manual, and we're gonna get through it together 🫶

---

✨ NAME ✨

cinder_backup_selinux — the Security Enhanced Linux Policy that's specifically for the cinder_backup processes. No cap, that's literally what it does 💖

---

🌸 DESCRIPTION 🌸

So, Security-Enhanced Linux — aka SELinux — secures the cinder_backup processes through flexible mandatory access control. It's like a very strict but loving bodyguard for your processes, iykyk ✨

The cinder_backup processes execute with the cinder_backup_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier.

Like, for example:

ps -eZ | grep cinder_backup_t

That's it, that's the vibe check for your processes 🔍

---

🚪 ENTRYPOINTS 🚪

The cinder_backup_t SELinux type can be entered via the cinder_backup_exec_t file type. Think of it as the VIP entrance to the domain, bestie 💅

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

/usr/bin/cinder-backup

Periodt, that's the one path 👑

---

👯 PROCESS TYPES 👯

SELinux defines process types (domains) for each process running on the system. Like, every process gets its own little domain, and that's iconic honestly 🎀

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

Policy governs the access confined processes have to files. The SELinux cinder_backup policy is very flexible, allowing users to setup their cinder_backup processes in as secure a method as possible. Lowkey obsessed with how customizable this is 😭

The following process types are defined for cinder_backup:

• cinder_backup_t

Note: semanage permissive -a cinder_backup_t can be used to make the process type cinder_backup_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. It's like, still watching you, just not blocking you 👀

---

🎛️ BOOLEANS 🎛️

SELinux policy is customizable based on least access required. The cinder_backup policy is extremely flexible and has several booleans that allow you to manipulate the policy and run cinder_backup with the tightest access possible. It's giving ✨ options ✨ and we love that for us 💖

If you want to dontaudit all daemons scheduling requests (setsched, sys_nice), you must turn on the daemons_dontaudit_scheduling boolean. Enabled by default, so you probably don't gotta touch it, but here's how just in case:

setsebool -P daemons_dontaudit_scheduling 1

If you want to deny user domains applications to map a memory region as both executable and writable, this is dangerous and the executable should be reported in bugzilla, you must turn on the deny_execmem boolean. Disabled by default — and honestly, keep it that way unless you know what you're doing, bestie 💀

setsebool -P deny_execmem 1

If you want to control the ability to mmap a low area of the address space, as configured by /proc/sys/vm/mmap_min_addr, you must turn on the mmap_low_allowed boolean. Disabled by default.

setsebool -P mmap_low_allowed 1

If you want to allow system to run with NIS, you must turn on the nis_enabled boolean. Disabled by default. NIS is giving retro but in an old-school way, ngl 🦋

setsebool -P nis_enabled 1

If you want to disable kernel module loading, you must turn on the secure_mode_insmod boolean. Disabled by default. Security queen behavior honestly 🔒

setsebool -P secure_mode_insmod 1

If you want to allow unconfined executables to make their heap memory executable — and listen, doing this is a really bad idea. Probably indicates a badly coded executable, but could indicate an attack. This executable should be reported in bugzilla — you must turn on the selinuxuser_execheap boolean. Disabled by default. No cap, don't do this unless you absolutely have to 😭

setsebool -P selinuxuser_execheap 1

If you want to allow unconfined executables to make their stack executable — and this should never, ever be necessary. Probably indicates a badly coded executable, but could indicate an attack. This executable should be reported in bugzilla — you must turn on the selinuxuser_execstack boolean. Disabled by default. Like, seriously, never ever fr fr 💀

setsebool -P selinuxuser_execstack 1

---

📂 MANAGED FILES 📂

The SELinux process type cinder_backup_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 is powerful but it doesn't override everything, iykyk 🫶

• file_type — all files on the system. Yeah, just... all of them. Main character energy, honestly 🌈

---

🏷️ FILE CONTEXTS 🏷️

SELinux requires files to have an extended attribute to define the file type. It's like every file has a little label, and that label is its whole identity 🎀

You can see the context of a file using the -Z option to ls.

Policy governs the access confined processes have to these files. The SELinux cinder_backup policy is very flexible, allowing users to setup their cinder_backup processes in as secure a method as possible. Flexible AND secure? We love a multitasking queen 💅

💖 STANDARD FILE CONTEXT 💖

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

Note: SELinux often uses regular expressions to specify labels that match multiple files. So those regexes are doing a lot of heavy lifting, bestie ✨

The following file types are defined for cinder_backup:

• cinder_backup_exec_t — Set files with the cinder_backup_exec_t type, if you want to transition an executable to the cinder_backup_t domain. This is the entry point, the VIP pass, the ✨ main gate ✨
• cinder_backup_tmp_t — Set files with the cinder_backup_tmp_t type, if you want to store cinder backup temporary files in the /tmp directories. Temp files gotta have their own label too, it's only fair 🍓
• cinder_backup_unit_file_t — Set files with the cinder_backup_unit_file_t type, if you want to treat the files as cinder backup unit content. Unit content gets its own type, and that's iconic 👑

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 the quick fix and semanage fcontext + restorecon is the forever fix, got it? 💖

---

🛠️ COMMANDS 🛠️

semanage fcontext can also be used to manipulate default file context mappings. It's the tool for making those labels permanent, bestie ✨

semanage permissive can also be used to manipulate whether or not a process type is permissive. So you can decide which domains get the lenient treatment 🦋

semanage module can also be used to enable/disable/install/remove policy modules. Modules are like little policy add-ons, and semanage module is your remote control for them 🎛️

semanage boolean can also be used to manipulate the booleans. All those booleans we talked about? This is how you flip them on and off 💅

system-config-selinux is a GUI tool available to customize SELinux policy settings. For when you want to point and click instead of type, and honestly? Valid 🌸

---

✍️ AUTHOR ✍️

This manual page was auto-generated using sepolicy manpage. So like, a robot wrote the original, but I'm here to give it some personality, y'know? 💖

---

👀 SEE ALSO 👀

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

All the related manuals you might wanna check out, bestie. Go read them, they're lowkey useful 🫶

---

And that's the whole thing, bestie! This was cinder_backup from 26-10-06, and the manual page is cinder_backup_selinux(8). You ate that, honestly. Go forth and SELinux with confidence ✨💅👑