[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference humane::scheduler

Title:	SCHEDULER
Notice:	Welcome to the Scheduler Conference on node HUMANEril
Moderator:	RUMOR::FALEK

Created:	Sat Mar 20 1993
Last Modified:	Tue Jun 03 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	1240
Total number of notes:	5017

1108.0. "Scheduler with C2 Security" by BSS::G_MCINTOSH (Touch Not the Cat, Bot the Glove) Thu May 23 1996 20:21

    
    Does anyone know of any known problems with running
    DecScheduler on a Unix box that has C2 Security, specifically,
    Kerberos running on it.
    
    Sometimes customer runs a job and it runs successfully, then other
    times he gets an error complaining about bad proxy, yet nothing
    changes.  This occurs intermittently and customer suspects C2
    security.
    
    Any known problems with Scheduler and C2?
    
    Thanks

T.R Title User Personal
Name Date Lines

1108.1 Don't think so...more specifics MUZICK::MORIARTY Thu May 23 1996 21:22 26

T.R	Title	User	Personal Name	Date	Lines
1108.1	Don't think so...more specifics	MUZICK::MORIARTY		`Thu May 23 1996 21:22`	26
	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.

    
    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.