condor_schedd_selinux(8)

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

✨ condor_schedd_selinux ✨ — like, the SELinux glow-up manual for condor_schedd 💅

okay bestie, buckle up 🎀 this is the condor_schedd_selinux(8) page, and it's literally all about the Security Enhanced Linux Policy for the condor_schedd processes. no cap, it's giving "mandatory access control but make it cute." 🦋

🌸 NAME 🌸

condor_schedd_selinux — Security Enhanced Linux Policy for the condor_schedd processes. periodt. 💖

✨ DESCRIPTION ✨

Security-Enhanced Linux secures the condor_schedd processes via flexible mandatory access control. like, it's literally the bouncer at the club but for syscalls. 🔥

The condor_schedd processes execute with the condor_schedd_t SELinux type. you can check if you have these processes running by executing the ps command with the -Z qualifier. vibe check time 👑

for example:

ps -eZ | grep condor_schedd_t

🦋 ENTRYPOINTS 🦋

The condor_schedd_t SELinux type can be entered via the condor_schedd_exec_t file type. that's the doorway, bestie 🚪✨

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

/usr/bin/condor_schedd

👑 PROCESS TYPES 👑

SELinux defines process types (domains) for each process running on the system. main character energy for every process, honestly. 💅

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

Policy governs the access confined processes have to files. SELinux condor_schedd policy is very flexible allowing users to setup their condor_schedd processes in as secure a method as possible. slay, security-wise. 🔐

The following process types are defined for condor_schedd:

  • condor_schedd_t
Note: semanage permissive -a condor_schedd_t can be used to make the process type condor_schedd_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so it's like, not grounded, but mom is still writing it down in the notebook 😭📓

🎀 BOOLEANS 🎀

SELinux policy is customizable based on least access required. condor_schedd policy is extremely flexible and has several booleans that allow you to manipulate the policy and run condor_schedd with the tightest access possible. literally least-privilege era 💜

  • daemons_dontaudit_scheduling — if you want to dontaudit all daemons scheduling requests (setsched, sys_nice), you must turn on this boolean. Enabled by default.
setsebool -P daemons_dontaudit_scheduling 1
  • fips_mode — if you want to allow all domains to execute in fips_mode, you must turn on this boolean. Enabled by default.
setsebool -P fips_mode 1
  • nis_enabled — if you want to allow system to run with NIS, you must turn on this boolean. Disabled by default.
setsebool -P nis_enabled 1

🌈 MANAGED FILES 🌈

The SELinux process type condor_schedd_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 not out here overriding your regular perms, bestie, they're a team 🫶

  • 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_schedd_tmp_t — (no default paths listed, she's mysterious like that 🙈)
  • 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

💖 FILE CONTEXTS 💖

SELinux requires files to have an extended attribute to define the file type. yes, every file needs its little label, it's called accessorizing ✨🏷️

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

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

🧚 STANDARD FILE CONTEXT 🧚

SELinux defines the file context types for the condor_schedd. 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. relocation era 💫

semanage fcontext -a -t condor_schedd_tmp_t
'/srv/condor_schedd/content(/.*)?'
restorecon -R -v /srv/mycondor_schedd_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex bestie, she contains multitudes 🌀

The following file types are defined for condor_schedd:

  • condor_schedd_exec_t — set files with the condor_schedd_exec_t type, if you want to transition an executable to the condor_schedd_t domain. the exec-to-domain pipeline, iconic 🔥
  • condor_schedd_tmp_t — set files with the condor_schedd_tmp_t type, if you want to store condor schedd temporary files in the /tmp directories. temp files stay in their lane 🍓
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 quick lil touch-up and semanage fcontext + restorecon is the full glam permanent makeover, iykyk 💅💖

⭐ 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 bestie, a whole GUI, for the clicky girlies 🖱️🌸

🎀 AUTHOR 🎀

This manual page was auto-generated using sepolicy manpage. the robots did this one, and honestly? they ate. 🤖✨

🦋 SEE ALSO 🦋

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

and that's the whole page, bestie 🫶✨ source/version vibes: condor_schedd, dated 26-10-06, living in condor_schedd_selinux(8) — go forth and label responsibly 💜🌸🎀

📦 where this page comes from