condor_procd_selinux(8)

πŸ“¦
version 20250627+git412.dbf877ab7 Β· 7 versions
, in opensuse-leap 16.0

πŸ’… condor_procd_selinux(8) β€” the SELinux Policy for condor_procd situation

okay bestie, so this is the manual page for condor_procd_selinux, aka the whole ✨SELinux policy✨ vibe for your condor_procd processes. buckle up, it's giving security but make it cute πŸŽ€


🌸 NAME 🌸

condor_procd_selinux β€” the Security Enhanced Linux Policy for the condor_procd processes. literally what it says on the tin, no cap πŸ’–


✨ DESCRIPTION ✨

Security-Enhanced Linux secures the condor_procd processes via flexible mandatory access control. yes queen, mandatory access control, it does not ask politely 🫢

The condor_procd processes execute with the condor_procd_t SELinux type. you can check if you've got these processes running by executing the ps command with the -Z qualifier. for example:

ps -eZ | grep condor_procd_t

go off, ps -eZ πŸ¦‹


πŸšͺ ENTRYPOINTS πŸšͺ

The condor_procd_t SELinux type can be entered via the condor_procd_exec_t file type. that's the door, that's the entrance, that's the moment πŸ’…

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

/usr/bin/condor_procd

one path, one icon, periodt ⭐


πŸ‘‘ PROCESS TYPES πŸ‘‘

SELinux defines process types (domains) for each process running on the system. yes, every process has its own little domain, main character energy fr fr 🌈

You can see the context of a process using the -Z option to ps. highly recommend, it's giving insight 😌

Policy governs the access confined processes have to files. SELinux condor_procd policy is very flexible, allowing users to setup their condor_procd processes in as secure a method as possible. flexible and secure, we love a multihyphenate πŸ’œ

The following process types are defined for condor_procd:

  • condor_procd_t
πŸ“Œ Note: semanage permissive -a condor_procd_t can be used to make the process type condor_procd_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, it won't block you but it WILL still be watching and taking notes πŸ‘€ not me reading the receipts

πŸ”˜ BOOLEANS πŸ”˜

SELinux policy is customizable based on least access required. condor_procd policy is extremely flexible and has several booleans that allow you to manipulate the policy and run condor_procd with the tightest access possible. booleans are basically lil toggle switches for your security vibe check 🎚️

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

the way -P makes it persistent… obsessed πŸ“


πŸ“ MANAGED FILES πŸ“

The SELinux process type condor_procd_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 says yes and then DAC can still say no, teamwork 😭

  • 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_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

like, that's a LOT of paths and every single one of them matters, don't skip a single one bestie πŸ’€


🏷️ FILE CONTEXTS 🏷️

SELinux requires files to have an extended attribute to define the file type. yes, files have labels now, we stan an organized king πŸ‘‘

You can see the context of a file using the -Z option to ls. go check your faves πŸ¦‹

Policy governs the access confined processes have to these files. SELinux condor_procd policy is very flexible, allowing users to setup their condor_procd processes in as secure a method as possible. (yes this sentence is iconic enough to appear twice πŸ’–)

⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for the condor_procd. 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.

semanage fcontext -a -t condor_procd_exec_t
'/srv/condor_procd/content(/.*)?'
restorecon -R -v /srv/mycondor_procd_content
πŸ“Œ Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies rise πŸ™ˆ

The following file types are defined for condor_procd:

  • condor_procd_exec_t β€” Set files with the condor_procd_exec_t type, if you want to transition an executable to the condor_procd_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. temporary vs permanent, know the difference, it's giving character development 😭

πŸ› οΈ 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 whole GUI, for the girlies who prefer clicking 🌸

✍️ AUTHOR ✍️

This manual page was auto-generated using sepolicy manpage. the robots wrote it, I just added the glitter ✨


πŸ‘€ SEE ALSO πŸ‘€

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


k that's the whole page bestie, you ate that read πŸ’… go forth and label responsibly 🫢

condor_procd β€” page dated 26-10-06 β€” condor_procd_selinux(8) πŸŽ€πŸ’–

πŸ“¦ where this page comes from