[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Remote repository permissions best practices

From: Jim.Hyslop
Subject: RE: Remote repository permissions best practices
Date: Mon, 28 Mar 2005 16:57:04 -0500

Todd Denniston wrote:
> 1) all the users who need write access to the repository 
> should be in the
> same UNIX group.
Doesn't this effectively negate any benefit of using groups? For example, in
our setup we want full-time staff to have general access to most of the
repository, and co-op students to have access only to those sections of the
repository they are working on. Certain sections of the repository are
3rd-party sources protected by an NDA, so only specific people (including
both full-time and possibly co-op students) have access to those sections.
How would you accomplish this by using a single group? We can't use
cvs_acls, because it only restricts access on check-in, not on check-out.

Jim Hyslop
Senior Software Designer
Leitch Technology International Inc. ( )
Columnist, C/C++ Users Journal ( )

reply via email to

[Prev in Thread] Current Thread [Next in Thread]