Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!ucsd!ucbvax!ubvms.BITNET!MASERIK
From: MASERIK@ubvms.BITNET (MAS-Polecat)
Newsgroups: misc.security
Subject: Re: Comments on Account Sharing Solution Solicited
Message-ID: <9012031558.AA24053@ucbarpa.Berkeley.EDU>
Date: 6 Nov 90 22:53:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 14
Approved: security@rutgers.edu


     I have a similar situation here at the University of Buffalo.  I have
several people programming for me on the same project.  To facilitate code
updates there is only one copy of the code and all of the work was done out of
one account (no flames, please I KNOW about libraries, ACLs, etc.).

     To provide user accountability for mail/send messages, printing, batch
jobs, etc. we created several new accounts (one for each programmer) and gave
them all the same UIC and login directory as the original programming account.
This also solves a problem with programmers giving out the password to their
friends, as they are less likely to do it if they are more accountable for
their actions.

Erik Bryant


Brought to you by Super Global Mega Corp .com