1condor_schedd_selinux(8) SELinux Policy condor_schedd condor_schedd_selinux(8)
2
6 condor_schedd_selinux - Security Enhanced Linux Policy for the con‐
7 dor_schedd processes
8
10 Security-Enhanced Linux secures the condor_schedd processes via flexi‐
11 ble mandatory access control.
12 The condor_schedd processes execute with the condor_schedd_t SELinux
14 type. You can check if you have these processes running by executing
15 the ps command with the -Z qualifier.
16 For example:
18 ps -eZ | grep condor_schedd_t
20
24 The condor_schedd_t SELinux type can be entered via the con‐
25 dor_schedd_exec_t file type.
26 The default entrypoint paths for the condor_schedd_t domain are the
28 following:
29 /usr/sbin/condor_schedd
31
33 SELinux defines process types (domains) for each process running on the
34 system
35 You can see the context of a process using the -Z option to ps
37 Policy governs the access confined processes have to files. SELinux
39 condor_schedd policy is very flexible allowing users to setup their
40 condor_schedd processes in as secure a method as possible.
41 The following process types are defined for condor_schedd:
43 condor_schedd_t
45 Note: semanage permissive -a condor_schedd_t can be used to make the
47 process type condor_schedd_t permissive. SELinux does not deny access
48 to permissive process types, but the AVC (SELinux denials) messages are
49 still generated.
50
53 SELinux policy is customizable based on least access required. con‐
54 dor_schedd policy is extremely flexible and has several booleans that
55 allow you to manipulate the policy and run condor_schedd with the
56 tightest access possible.
57 If you want to allow all domains to execute in fips_mode, you must turn
61 on the fips_mode boolean. Enabled by default.
62 setsebool -P fips_mode 1
64
68 The SELinux process type condor_schedd_t can manage files labeled with
69 the following file types. The paths listed are the default paths for
70 these file types. Note the processes UID still need to have DAC per‐
71 missions.
72 cluster_conf_t
74 /etc/cluster(/.*)?
76 cluster_var_lib_t
78 /var/lib/pcsd(/.*)?
80 /var/lib/cluster(/.*)?
81 /var/lib/openais(/.*)?
82 /var/lib/pengine(/.*)?
83 /var/lib/corosync(/.*)?
84 /usr/lib/heartbeat(/.*)?
85 /var/lib/heartbeat(/.*)?
86 /var/lib/pacemaker(/.*)?
87 cluster_var_run_t
89 /var/run/crm(/.*)?
91 /var/run/cman_.*
92 /var/run/rsctmp(/.*)?
93 /var/run/aisexec.*
94 /var/run/heartbeat(/.*)?
95 /var/run/pcsd-ruby.socket
96 /var/run/corosync-qnetd(/.*)?
97 /var/run/corosync-qdevice(/.*)?
98 /var/run/corosync.pid
99 /var/run/cpglockd.pid
100 /var/run/rgmanager.pid
101 /var/run/cluster/rgmanager.sk
102 condor_conf_t
104 /etc/condor(/.*)?
106 condor_log_t
108 /var/log/condor(/.*)?
110 condor_schedd_tmp_t
112 condor_var_lib_t
115 /var/lib/condor(/.*)?
117 /var/lib/condor/spool(/.*)?
118 /var/lib/condor/execute(/.*)?
119 condor_var_lock_t
121 /var/lock/condor(/.*)?
123 condor_var_run_t
125 /var/run/condor(/.*)?
127 krb5_host_rcache_t
129 /var/tmp/krb5_0.rcache2
131 /var/cache/krb5rcache(/.*)?
132 /var/tmp/nfs_0
133 /var/tmp/DNS_25
134 /var/tmp/host_0
135 /var/tmp/imap_0
136 /var/tmp/HTTP_23
137 /var/tmp/HTTP_48
138 /var/tmp/ldap_55
139 /var/tmp/ldap_487
140 /var/tmp/ldapmap1_0
141 root_t
143 /sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
145 /
146 /initrd
147
150 SELinux requires files to have an extended attribute to define the file
151 type.
152 You can see the context of a file using the -Z option to ls
154 Policy governs the access confined processes have to these files.
156 SELinux condor_schedd policy is very flexible allowing users to setup
157 their condor_schedd processes in as secure a method as possible.
158 STANDARD FILE CONTEXT
160 SELinux defines the file context types for the condor_schedd, if you
162 wanted to store files with these types in a diffent paths, you need to
163 execute the semanage command to specify alternate labeling and then use
164 restorecon to put the labels on disk.
165 semanage fcontext -a -t condor_schedd_tmp_t '/srv/mycondor_schedd_con‐
167 tent(/.*)?'
168 restorecon -R -v /srv/mycondor_schedd_content
169 Note: SELinux often uses regular expressions to specify labels that
171 match multiple files.
172 The following file types are defined for condor_schedd:
174 condor_schedd_exec_t
178 - Set files with the condor_schedd_exec_t type, if you want to transi‐
180 tion an executable to the condor_schedd_t domain.
181 condor_schedd_tmp_t
185 - Set files with the condor_schedd_tmp_t type, if you want to store
187 condor schedd temporary files in the /tmp directories.
188 Note: File context can be temporarily modified with the chcon command.
192 If you want to permanently change the file context you need to use the
193 semanage fcontext command. This will modify the SELinux labeling data‐
194 base. You will need to use restorecon to apply the labels.
195
198 semanage fcontext can also be used to manipulate default file context
199 mappings.
200 semanage permissive can also be used to manipulate whether or not a
202 process type is permissive.
203 semanage module can also be used to enable/disable/install/remove pol‐
205 icy modules.
206 semanage boolean can also be used to manipulate the booleans
208 system-config-selinux is a GUI tool available to customize SELinux pol‐
211 icy settings.
212
215 This manual page was auto-generated using sepolicy manpage .
216
219 selinux(8), condor_schedd(8), semanage(8), restorecon(8), chcon(1), se‐
220 policy(8), setsebool(8)
221condor_schedd 21-11-19 condor_schedd_selinux(8)