info-cvs
[Top][All Lists]
Advanced

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

Re: Repository Access


From: S I
Subject: Re: Repository Access
Date: Thu, 16 Jun 2005 11:00:36 -0700

cvs_acls? Ok thanks. I have to research that. Is that a 3rd party tool or part of CVS?

----Original Message Follows----
From: Todd Denniston <address@hidden>
To: S I <address@hidden>
CC: address@hidden
Subject: Re: Repository Access
Date: Thu, 16 Jun 2005 08:56:09 -0500
MIME-Version: 1.0
Received: from mail.ssa.crane.navy.mil ([164.227.42.3]) by mc3-f29.hotmail.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 16 Jun 2005 06:56:10 -0700 Received: from ssa.crane.navy.mil (address@hidden [164.227.42.142]) by mail.ssa.crane.navy.mil with ESMTP id IAA25670; Thu, 16 Jun 2005 08:57:11 -0500
X-Message-Info: JGTYoYF78jGyC0d8LB2jTso0kYQInfoqWjVpkDHFtCs=
Organization: Code 6067, NSWC Crane
X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.2.25glock1 i686)
X-Accept-Language: en
References: <address@hidden> <address@hidden>
Return-Path: address@hidden
X-OriginalArrivalTime: 16 Jun 2005 13:56:10.0860 (UTC) FILETIME=[26DEB2C0:01C5727B]

Jim Hyslop wrote:
>
> S I wrote:
> > Hi Class!
> >
> > Currently our CVS repo has 3 main & separate projects running under it.
> > By default when I create a new unix user; I give them access to the
> > whole repository, however, some folks have been editing files in
> > projects they were not supposed to.
>
> > How can I ONLY and specifically create or modify the access rights &
> > privileges of only few specific people w/o wreaking havoc on the whole
> > repository? And by default if they're not listed in that file then that
> > means they have access to all projs?  Is there a way?
>
> Use your operating system's access control system. Create a group for
> each project, and assign people to the groups they are allowed to be in.
> You will have to determine, in conjunction with your project leaders,
> which projects new users will have access to, by default.
>
> And, of course, get the managers and project leaders on side to explain
> that changing project files they haven't been assigned to will result in
> disciplinary action, up to and including termination.

Although the above is what I also see as the best option, you *MAY* also be
able to get some where in the middle using the cvs_acls script.

--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter






reply via email to

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