ajaxterm_selinux(8)

📦 version 38.1.87, in centos-stream 9

💖 ajaxterm_selinux — the SELinux glow-up for ajaxterm processes 💖

okay bestie, so this is ajaxterm_selinux(8), the SELinux policy page for ajaxterm, and I'm literally about to walk you through every single thing on it because it's lowkey important and highkey iconic 🌈✨

So like, ajaxterm_selinux is the Security Enhanced Linux Policy for the ajaxterm processes — yes that's the whole NAME section, slay 💅

✨ DESCRIPTION ✨

Security-Enhanced Linux secures the ajaxterm processes via flexible mandatory access control. That's the whole vibe — SELinux just keeps ajaxterm on a leash so it can't go rogue, and honestly? iconic 🎀

The ajaxterm processes execute with the ajaxterm_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier. Like this, bestie:

ps -eZ | grep ajaxterm_t

That's literally it. Run that and you'll see if ajaxterm_t is out there living its main character energy 🦋

🌸 ENTRYPOINTS 🌸

The ajaxterm_t SELinux type can be entered via the ajaxterm_exec_t file type.

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

  • /usr/share/ajaxterm/ajaxterm.py

That's the one way in, periodt 👑

💜 PROCESS TYPES 💜

So SELinux defines process types (domains) for each process running on the system. You can see the context of a process using the -Z option to ps. No cap, that's just how it works.

Policy governs the access confined processes have to files. SELinux ajaxterm policy is very flexible, allowing users to setup their ajaxterm processes in as secure a method as possible. We love a flexible queen who still respects boundaries 🫶

The following process types are defined for ajaxterm:

  • ajaxterm_t
  • ajaxterm_ssh_t
Note: semanage permissive -a ajaxterm_t can be used to make the process type ajaxterm_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So like, permissive mode means it won't block you, but the receipts (AVC messages) are still being kept, iykyk 👀

⭐ BOOLEANS ⭐

SELinux policy is customizable based on least access required. ajaxterm policy is extremely flexible and has several booleans that allow you to manipulate the policy and run ajaxterm with the tightest access possible. Literally the "give them nothing but what they need" philosophy and we're obsessed 💅

  • Want to dontaudit all daemons scheduling requests (setsched, sys_nice)? You must turn on the daemons_dontaudit_scheduling boolean. It's enabled by default, so it's already serving its purpose bestie.
setsebool -P daemons_dontaudit_scheduling 1
  • 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, periodt 🔥
setsebool -P fips_mode 1
  • Want to allow confined applications to use nscd shared memory? You must turn on the nscd_use_shm boolean. Enabled by default, as she should be 💖
setsebool -P nscd_use_shm 1

Three booleans, all enabled by default, all slaying in their own lane 🎀

🎀 MANAGED FILES 🎀

The SELinux process type ajaxterm_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 — so even if SELinux says it's chill, the regular Unix permissions still have a say, okay? Both checks have to pass, no shortcuts 🙈

  • ajaxterm_var_run_t
    • /var/run/ajaxterm.pid
  • cluster_conf_t
    • /etc/cluster(/.*)?
  • cluster_var_lib_t
    • /var/lib/pcsd(/.*)?
    • /var/lib/cluster(/.*)?
    • /var/lib/openais(/.*)?
    • /var/lib/pengine(/.*)?
    • /var/lib/corosync(/.*)?
    • /usr/lib/heartbeat(/.*)?
    • /var/lib/heartbeat(/.*)?
    • /var/lib/pacemaker(/.*)?
  • cluster_var_run_t
    • /var/run/crm(/.*)?
    • /var/run/cman_.*
    • /var/run/rsctmp(/.*)?
    • /var/run/aisexec.*
    • /var/run/heartbeat(/.*)?
    • /var/run/pcsd-ruby.socket
    • /var/run/corosync-qnetd(/.*)?
    • /var/run/corosync-qdevice(/.*)?
    • /var/run/pcsd.socket
    • /var/run/corosync.pid
    • /var/run/cpglockd.pid
    • /var/run/rgmanager.pid
    • /var/run/cluster/rgmanager.sk
  • root_t
    • /sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
    • /
    • /initrd
  • ssh_home_t
    • /var/lib/[^/]+/.ssh(/.*)?
    • /root/.ssh(/.*)?
    • /var/lib/one/.ssh(/.*)?
    • /var/lib/pgsql/.ssh(/.*)?
    • /var/lib/openshift/[^/]+/.ssh(/.*)?
    • /var/lib/amanda/.ssh(/.*)?
    • /var/lib/stickshift/[^/]+/.ssh(/.*)?
    • /var/lib/gitolite/.ssh(/.*)?
    • /var/lib/nocpulse/.ssh(/.*)?
    • /var/lib/gitolite3/.ssh(/.*)?
    • /var/lib/openshift/gear/[^/]+/.ssh(/.*)?
    • /root/.shosts
    • /home/[^/]+/.ssh(/.*)?
    • /home/[^/]+/.ansible/cp/.*
    • /home/[^/]+/.shosts

That's a lot of file types and honestly each one is eating in its own way. ssh_home_t in particular is literally the moment with all those SSH paths 💀

🦋 FILE CONTEXTS 🦋

SELinux requires files to have an extended attribute to define the file type. You can see the context of a file using the -Z option to ls. Yes, ls -Z, your new bestie.

Policy governs the access confined processes have to these files. SELinux ajaxterm policy is very flexible, allowing users to setup their ajaxterm processes in as secure a method as possible. Same energy as before, still iconic 🌈

🌸 STANDARD FILE CONTEXT 🌸

SELinux defines the file context types for the ajaxterm. 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. Here's the whole glow-up in action:

semanage fcontext -a -t ajaxterm_var_run_t '/srv/myajaxterm_content(/.*)?'
restorecon -R -v /srv/myajaxterm_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. Regex is literally everywhere in SELinux and that's just the way it is bestie 🧚

The following file types are defined for ajaxterm:

  • ajaxterm_exec_t — Set files with the ajaxterm_exec_t type, if you want to transition an executable to the ajaxterm_t domain.
  • ajaxterm_initrc_exec_t — Set files with the ajaxterm_initrc_exec_t type, if you want to transition an executable to the ajaxterm_initrc_t domain.
  • ajaxterm_var_run_t — Set files with the ajaxterm_var_run_t type, if you want to store the ajaxterm files under the /run or /var/run directory.
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 that doesn't stick, and semanage fcontext + restorecon is the real permanent glow-up ✨

💅 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. Yes, a GUI, for when you don't feel like typing everything, no judgement 🫶

🌟 AUTHOR 🌟

This manual page was auto-generated using sepolicy manpage. So like, a bot wrote the original and I'm just giving it the personality it deserved 💅✨

👑 SEE ALSO 👑

selinux(8), ajaxterm(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8), ajaxterm_ssh_selinux(8), ajaxterm_ssh_selinux(8)

And yes, ajaxterm_ssh_selinux(8) is listed twice in the original — I'm not fixing that, I'm just reporting the facts. She said it twice, and honestly? Maybe she needed us to hear it twice 💀💖

🌈💜 this page is from ajaxterm and its version is 26-10-23, dated 26-10-23 (yes both, that's what the footer says), and that's the whole manual page bestie — now go check your SELinux contexts and slay, periodt 💜🌈

📦 where this page comes from