CONDOR_STARTD_SSH_SELINUX(8)
π
condor_startd_ssh_selinux(8) β the SELinux glow-up for condor_startd_ssh
okay bestie, welcome to the manual page for condor_startd_ssh_selinux, which is the SELinux policy situation for the condor_startd_ssh processes. it's from the SELinux Policy corner of the man-page universe and honestly? she's iconic. let's get into it π
β¨ NAME β¨
condor_startd_ssh_selinux β Security Enhanced Linux Policy for the condor_startd_ssh processes. that's it, that's the name, no notes π
π¦ DESCRIPTION π¦
Security-Enhanced Linux secures the condor_startd_ssh processes via flexible mandatory access control. yes, mandatory β SELinux is the friend who does not accept "i'll do it later" as an answer, and honestly good for her.
The condor_startd_ssh processes execute with the condor_startd_ssh_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_startd_ssh_t
run it, see what's up, vibe check the output, slay π₯
πͺ ENTRYPOINTS πͺ
The condor_startd_ssh_t SELinux type can be entered via the ssh_exec_t file type. that's the doorway, bestie πͺβ¨
the default entrypoint paths for the condor_startd_ssh_t domain are the following, exact as they come:
/usr/bin/ssh, /usr/libexec/nm-ssh-service
π PROCESS TYPES π
SELinux defines process types (domains) for each process running on the system. very "everyone gets their own little label" of it all, and we love that for them.
you can see the context of a process using the -Z option to ps. yes, -Z again. she's the main character of this section.
policy governs the access confined processes have to files. SELinux condor_startd_ssh policy is very flexible, allowing users to setup their condor_startd_ssh processes in as secure a method as possible. flexible and secure? highkey a vibe πΈ
the following process types are defined for condor_startd_ssh:
condor_startd_ssh_t
Note:semanage permissive -a condor_startd_ssh_tcan be used to make the process typecondor_startd_ssh_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, she's chill about it but she's still watching π
π BOOLEANS π
SELinux policy is customizable based on least access required. condor_startd_ssh policy is extremely flexible and has several booleans that allow you to manipulate the policy and run condor_startd_ssh with the tightest access possible. tightest access possible = the most locked-down, no extras, boundaries-up energy π«Ά
fips_modeβ if you want to allow all domains to execute infips_mode, you must turn on thefips_modeboolean. Enabled by default.
setsebool -P fips_mode 1
nis_enabledβ if you want to allow system to run with NIS, you must turn on thenis_enabledboolean. Disabled by default.
setsebool -P nis_enabled 1
π MANAGED FILES π
The SELinux process type condor_startd_ssh_t can manage files labeled with the following file types. the paths listed are the default paths for these file types. note β and this is important, bestie β the processes UID still need to have DAC permissions. SELinux is not out here overriding DAC, she's just adding her own layer of gorgeousness on top π
condor_var_lib_t
/var/lib/condor(/.*)?
/var/lib/condor/spool(/.*)?
/var/lib/condor/execute(/.*)?
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
ssh_home_t
/var/lib/[^/]+/.ssh(/.*)?
/root/.ssh(/.*)?
/var/lib/one/.ssh(/.*)?
/srv/gitolite/.ssh(/.*)?
/srv/gitolite3/.ssh(/.*)?
/var/lib/pgsql/.ssh(/.*)?
/var/lib/openshift/[^/]+/.ssh(/.*)?
/var/lib/amanda/.ssh(/.*)?
/var/lib/stickshift/[^/]+/.ssh(/.*)?
/var/lib/nocpulse/.ssh(/.*)?
/var/lib/openshift/gear/[^/]+/.ssh(/.*)?
/root/.shosts
/home/[^/]+/.ssh(/.*)?
/home/[^/]+/.ansible/cp/.*
/home/[^/]+/.shosts
like, look at that list. .ssh directories everywhere, a whole little extended family of them ππ
π οΈ COMMANDS π οΈ
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 whole GUI, for the girlies who prefer clicking to typing β¨
π AUTHOR π
This manual page was auto-generated using sepolicy manpage . β yes, auto-generated, she didn't even have to lift a finger, and yet she ate π«Ά
π SEE ALSO π
selinux(8), condor_startd_ssh(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8)
go read those too, iykyk ππ
and that's the whole page, bestie β this little masterpiece comes to you as condor_startd_ssh, dated 26-10-06, under the title condor_s...h_selinux(8). mwah, go forth and be secure πππ¦π·
π¦ 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