condor_master_selinux(8)

🌈 condor_master_selinux(8) — the SELinux glow-up for condor_master 💅

okay bestie, welcome to condor_master_selinux(8), the manual page that explains the Security Enhanced Linux Policy for the condor_master processes. yes, that's a lot of words, but it's literally just "how do we keep condor_master safe and also make sure it can still do its job" ✨

---

💖 NAME 💖

condor_master_selinux — the Security Enhanced Linux Policy for the condor_master processes. that's it, that's the name, and honestly it ate 🫶

---

✨ DESCRIPTION ✨

Security-Enhanced Linux secures the condor_master processes via flexible mandatory access control. mandatory access control is the strict parent in this situation, and honestly it's iconic.

The condor_master processes execute with the condor_master_t SELinux type. you can check if you have these processes running by executing the ps command with the -Z qualifier. vibe check your processes, bestie 👑

For example:

ps -eZ | grep condor_master_t

run that and you'll see exactly which of your processes are living that condor_master_t life 💅

---

🚪 ENTRYPOINTS 🚪

The condor_master_t SELinux type can be entered via the condor_master_exec_t file type. so that's the doorway — the one and only ✨

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

/usr/bin/condor_master

just the one path, and it's a main character for sure 🎀

---

👯 PROCESS TYPES 👯

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

You can see the context of a process using the -Z option to ps. -Z is the tell-me-everything flag, ilysm 🫶

Policy governs the access confined processes have to files. SELinux condor_master policy is very flexible allowing users to setup their condor_master processes in as secure a method as possible. flexible and secure? we love a both/and situation 🌸

The following process types are defined for condor_master:

condor_master_t

Note: semanage permissive -a condor_master_t can be used to make the process type condor_master_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, it stops blocking stuff but it still snitches in the logs, ngl 💀

---

🎛️ BOOLEANS 🎛️

SELinux policy is customizable based on least access required. condor_master policy is extremely flexible and has several booleans that allow you to manipulate the policy and run condor_master with the tightest access possible. booleans are basically little on/off switches for the vibes, and there are options here — slay ✨

If you want to dontaudit all daemons scheduling requests (setsched, sys_nice), you must turn on the daemons_dontaudit_scheduling boolean. Enabled by default.

setsebool -P daemons_dontaudit_scheduling 1

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

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

that's three booleans, all accounted for, no gatekeeping here 💖

---

📁 MANAGED FILES 📁

The SELinux process type condor_master_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 like, SELinux letting you in is not the same as the file permissions letting you in — both bouncers gotta approve you 😭

• 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

/run/crm(/.*)?
/run/cman_.*
/run/rsctmp(/.*)?
/run/aisexec.*
/run/heartbeat(/.*)?
/run/pcsd-ruby.socket
/run/corosync-qnetd(/.*)?
/run/corosync-qdevice(/.*)?
/run/pcsd.socket
/run/corosync.pid
/run/cpglockd.pid
/run/rgmanager.pid
/run/cluster/rgmanager.sk

• condor_conf_t

/etc/condor(/.*)?

• condor_log_t

/var/log/condor(/.*)?

• condor_master_tmp_t

(no default paths listed for this one — it's mysterious, it's enigmatic, we respect it 🙈)

• condor_var_lib_t

/var/lib/condor(/.*)?
/var/lib/condor/spool(/.*)?
/var/lib/condor/execute(/.*)?

• condor_var_lock_t

/run/lock/condor(/.*)?

• condor_var_run_t

/run/condor(/.*)?

• 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

• root_t

/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
/var/lib/ntp

every single one, right there, not a crumb skipped 🍓

---

🏷️ FILE CONTEXTS 🏷️

SELinux requires files to have an extended attribute to define the file type. yes, files have vibes and the vibes are stored in extended attributes, that's just how it is.

You can see the context of a file using the -Z option to ls. same -Z energy, different command, love that for us 💜

Policy governs the access confined processes have to these files. SELinux condor_master policy is very flexible allowing users to setup their condor_master processes in as secure a method as possible.

🌟 STANDARD FILE CONTEXT 🌟

SELinux defines the file context types for the condor_master. 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. relocating files? valid. forgetting restorecon? not valid, bestie 😤

semanage fcontext -a -t condor_master_exec_t '/srv/condor_master/content(/.*)?'
restorecon -R -v /srv/mycondor_master_content

Note: SELinux often uses regular expressions to specify labels that match multiple files. regex is doing a lot of heavy lifting here and honestly, respect 👑

The following file types are defined for condor_master:

• condor_master_exec_t — Set files with the condor_master_exec_t type, if you want to transition an executable to the condor_master_t domain. this is the doorway, the portal, the transition moment ✨
• condor_master_tmp_t — Set files with the condor_master_tmp_t type, if you want to store condor master temporary files in the /tmp directories. temp files stay temp files, we don't get attached 🎀

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 fix vs permanent fix, know the difference or you WILL be back here, fr fr 😭

---

🛠️ 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. a GUI! for the girlies who like a visual, no cap 💅

---

✍️ AUTHOR ✍️

This manual page was auto-generated using sepolicy manpage. robot-authored but make it fashion 🤖✨

---

👀 SEE ALSO 👀

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

---

and that's the whole page, bestie! this was condor_master — page condor_master_selinux(8), dated 26-10-06 — auto-generated, gatekept by no one, and now fully understood by you. go forth and label things correctly 🦋💖🌈