|
Scheduler does nothing imparticular for C2 compliance.
However, if the proxy mechanism is setup correctly there
should be no reason for a problem. I assume the job is
the same with the same user using the same server and
agent, if not there is your explanation. If everything
is the same there is no reason for getting a bad proxy
intermittently. The Scheduler is using the system service
ruserok mechanism which is part of Digital UNIX platform.
C2 does support of this system service, but does require
the .rhosts file have the following protections (i.e is
the root account):
# ls -l /.rhosts
-rw------- 1 root system 308 Jan 22 18:23 /.rhosts
#
Kerberos does not come into play here as far as Schdduler goes
to my understanding except for the network traffic accessing
the system but is not an issue.
Any insights or further details will certainly be helpful
if there is something more we can work with.
|