Path: utzoo!attcan!uunet!sdrc!crgabb
From: crgabb@sdrc.UUCP (Rob Gabbard)
Newsgroups: comp.sys.apollo
Subject: Re: ACLs
Summary: Project lists will do what you want
Message-ID: <490@sdrc.UUCP>
Date: 7 Jan 89 16:28:18 GMT
References: <40b47aa32.000bf2e@caen.engin.umich.edu> <856@nosc.NOSC.MIL>
Organization: Structural Dynamics Research Corp., Cincinnati
Lines: 30

In article <856@nosc.NOSC.MIL>, dennis@peanuts.nosc.mil (Dennis Cottel) writes:
> But ACLs can't do groups nicely either.  Suppose you want a group of
> people to have read/write access to a project directory.  So before

At Sr10 Apollo has fully implemented the Berkley Project List concept.
If someone is logged in as joe.research and wants access to a file whose
group is marketing he will be given access if he is allowed to be a member
of the marketing group (i.e. if he is included in marketing's membership
list in the registry).  This pertains to Domain/OS BSD4.3 and can be used
for Domain/OS Aegis and Sys VR3 if the PROJLIST environment variable is set
to true. With edrgy you can do some fancy things like restricting a group
from being in a project list (e.g. if that group is not the accounts primary
group it will not appear in his project list even if the user is a member
of that group).

They implemented a semi-form of Project Lists at SR9.5 Domain/IX but it didn't
work too well.






-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rob Gabbard (uunet!sdrc!crgabb)                 _    /|
Workstation Systems Programmer                  \'o.O'
Structural Dynamics Research Corporation        =(___)=   
                                                   U
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=