ricci_mo..._selinux(8)

📦
version 20250627+git412.dbf877ab7 · 7 versions
, in opensuse-leap 16.0

💅 ricci_modservice_selinux — the SELinux policy for ricci_modservice, but make it make sense

Okay bestie, so this is the manual page for ricci_modservice_selinux(8), and we're gonna get into how Security-Enhanced Linux does its thing for the ricci_modservice processes. No cap, it's actually kinda iconic once you get the vibe. Let's go 🫶

✨ NAME ✨

ricci_modservice_selinux — the Security Enhanced Linux Policy for the ricci_modservice processes. That's it, that's the whole name. Periodt.

🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the ricci_modservice processes via flexible mandatory access control. Literally what it says on the tin.

The ricci_modservice processes execute with the ricci_modservice_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier — it's giving "show me the labels" energy.

For example:

ps -eZ | grep ricci_modservice_t

Run that and you'll see what's up. Slay.

🦋 ENTRYPOINTS 🦋

The ricci_modservice_t SELinux type can be entered via the ricci_modservice_exec_t file type. Think of it like the VIP door into the domain, iykyk.

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

/usr/libexec/ricci-modservice

That's the one and only path listed, bestie. Don't come for me, I'm just the messenger. 💅

👑 PROCESS TYPES 👑

SELinux defines process types (domains) for each process running on the system. Cute, right?

You can see the context of a process using the -Z option to ps. Yes, -Z again — it's the moment.

Policy governs the access confined processes have to files. SELinux ricci_modservice policy is very flexible, allowing users to setup their ricci_modservice processes in as secure a method as possible. We love a flexible icon.

The following process types are defined for ricci_modservice:

  • ricci_modservice_t
Note: semanage permissive -a ricci_modservice_t can be used to make the process type ricci_modservice_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So like, it's not a free pass, it's just a "we're still watching" situation. 🙈

🎀 BOOLEANS 🎀

SELinux policy is customizable based on least access required. ricci_modservice policy is extremely flexible and has several booleans that allow you to manipulate the policy and run ricci_modservice with the tightest access possible. Fancy.

If you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean. Enabled by default. She's already on, no need to touch unless you're changing things.

setsebool -P fips_mode 1

That's the command if you ever need it. -P makes it persistent, so it survives a reboot — very main character of it. ✨

🔥 FILE CONTEXTS 🔥

SELinux requires files to have an extended attribute to define the file type. It's not like regular file permissions, it's the whole vibe check of the file.

You can see the context of a file using the -Z option to ls. Again with the -Z, we stan a consistent queen.

Policy governs the access confined processes have to these files. SELinux ricci_modservice policy is very flexible, allowing users to setup their ricci_modservice processes in as secure a method as possible. Same energy as before, but now it's about files.

🌈 STANDARD FILE CONTEXT 🌈

SELinux defines the file context types for the ricci_modservice. 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. It's a two-step slay.

semanage fcontext -a -t ricci_modservice_exec_t '/srv/ricci_modservice/content(/.*)?'
restorecon -R -v /srv/myricci_modservice_content

Run those in order, no cap. The first one tells SELinux about the new path pattern, the second one actually applies the labels. 🧚

Note: SELinux often uses regular expressions to specify labels that match multiple files. So that (/.*)? is doing a lot of heavy lifting — it's the regex representation of "and everything under here". Respect.

The following file types are defined for ricci_modservice:

  • ricci_modservice_exec_t — Set files with the ricci_modservice_exec_t type, if you want to transition an executable to the ricci_modservice_t domain. Basically: label it right, and it becomes a VIP.
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 the messy temporary fix, semanage fcontext + restorecon is the real permanent glow-up. Don't mix them up, 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. For the girlies who prefer a visual moment. 🎨

⭐ AUTHOR ⭐

This manual page was auto-generated using sepolicy manpage. Not me writing it by hand, the machine did it. Still cute though. 🤖

🍓 SEE ALSO 🍓

Go check out these other pages if you want the full lore:

Okay that's the whole page, bestie! You made it to the end, so proud of you. 🥹 This was ricci_modservice from 26-10-06 — go off and SELinux responsibly. Mwah! 💖✨

📦 where this page comes from