CONDOR_NEGOTIATOR_SELINUX(8)
π condor_negotiator_selinux β the SELinux glow-up for your condor_negotiator processes π
Okay bestie, so this is the condor_negotiator_selinux manual page β it's living in the SELinux Policy section of the manual, and honestly? It's giving "niche but iconic." Let's get into it.
β¨ NAME β¨
So condor_negotiator_selinux is literally the Security Enhanced Linux Policy for the condor_negotiator processes. That's the whole vibe. π
πΈ DESCRIPTION πΈ
Security-Enhanced Linux secures the condor_negotiator processes via flexible mandatory access control. No cap β that's what it does. π
The condor_negotiator processes execute with the condor_negotiator_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier.
For example:
ps -eZ | grep condor_negotiator_t
See? Easy. You got this. π«Ά
π¦ ENTRYPOINTS π¦
The condor_negotiator_t SELinux type can be entered via the condor_negotiator_exec_t file type. That's the doorway, bestie. πͺβ¨
The default entrypoint paths for the condor_negotiator_t domain are the following:
/usr/bin/condor_negotiator
Periodt. That's the only one. π
π PROCESS TYPES π
SELinux defines process types (domains) for each process running on the system. It's like every process gets its own little label, and honestly? Main character energy. π
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_negotiator policy is very flexible, allowing users to setup their condor_negotiator processes in as secure a method as possible. Lowkey obsessed with how customizable this is. π
The following process types are defined for condor_negotiator:
condor_negotiator_t
Note:semanage permissive -a condor_negotiator_tcan be used to make the process typecondor_negotiator_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So like, it's chill but it's still watching you. π
π BOOLEANS π
SELinux policy is customizable based on least access required. The condor_negotiator policy is extremely flexible and has several booleans that allow you to manipulate the policy and run condor_negotiator with the tightest access possible. It's giving "customize your privacy settings" but for processes. πβ¨
- If you want to dontaudit all daemons scheduling requests (
setsched,sys_nice), you must turn on thedaemons_dontaudit_schedulingboolean. 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 thefips_modeboolean. Enabled by default.
setsebool -P fips_mode 1
- If you want to allow system to run with NIS, you must turn on the
nis_enabledboolean. Disabled by default.
setsebool -P nis_enabled 1
Slay. Now you know which switches to flip. π
π§ MANAGED FILES π§
The SELinux process type condor_negotiator_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 isn't doing everything for you, bestie. You still gotta have the perms. π
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 file types, but you got this. π¦
π FILE CONTEXTS π
SELinux requires files to have an extended attribute to define the file type. It's like every file has a little name tag. So fetch. π
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_negotiator policy is very flexible, allowing users to setup their condor_negotiator processes in as secure a method as possible. Yes, we're saying "flexible" again β because it is. π
STANDARD FILE CONTEXT
SELinux defines the file context types for condor_negotiator. 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_negotiator_exec_t '/srv/condor_negotiator/content(/.*)?'
restorecon -R -v /srv/mycondor_negotiator_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. So like, regex is doing a lot of heavy lifting here. iykyk. π
The following file types are defined for condor_negotiator:
condor_negotiator_exec_t
- Set files with the
condor_negotiator_exec_ttype, if you want to transition an executable to thecondor_negotiator_tdomain.
Note: File context can be temporarily modified with thechconcommand. If you want to permanently change the file context you need to use thesemanage fcontextcommand. This will modify the SELinux labeling database. You will need to userestoreconto apply the labels. So like,chconis the quick fix,semanage fcontextis the real deal. Don't forgetrestoreconor it won't stick. π
β COMMANDS β
Okay so here's the toolset, bestie:
semanage fcontextcan also be used to manipulate default file context mappings.semanage permissivecan also be used to manipulate whether or not a process type is permissive.semanage modulecan also be used to enable/disable/install/remove policy modules.semanage booleancan also be used to manipulate the booleans.system-config-selinuxis a GUI tool available to customize SELinux policy settings. (A GUI? In my SELinux? It's more likely than you think. π₯οΈβ¨)
π AUTHOR π
This manual page was auto-generated using sepolicy manpage. So like, a robot wrote the original. Respect. π€π
π₯ SEE ALSO π₯
selinux(8), condor_negotiator(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8)
Like, read those too if you wanna be a SELinux scholar. Periodt. π
And that's the whole page, bestie! This was condor_negotiator manual page, dated 26-10-06, version condor_n...r_selinux(8). Go forth and negotiate those condors securely. π¦πβ¨
π¦ where this page comes from
- opensuse-leap 16.0: selinux-policy-doc 20250627+git412.dbf877ab7-160000.1.1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms