[Top][All Lists]

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

Re: How to add login feature to cvs

From: surinder singh
Subject: Re: How to add login feature to cvs
Date: Tue, 03 Oct 2000 19:26:55 +0530

Thanks Dave again.
It was exactly what I was looking for.


Dave Sherohman wrote:

> (I suspect that you wanted your response to my earlier message to go to the
> cvs list, but you only sent it to me.)
> On Sat, Sep 30, 2000 at 11:19:09AM +0530, surinder singh wrote:
> > Now I am using cvs as by creating the repository using #cvs init in user's 
> > home
> > directory. But only that user will have access to write into that 
> > repository. If
> > I create the repository in /usr say then nobody else than root can write 
> > into
> > that ( my own perception ) as write permission is set for root only. we can
> > change write permission to all but than there is no security.
> That's where groups come in.  For a repository in /usr, create a 'cvs' group
> (addgroup cvs), change the directory's group ownership to cvs (chgrp -R cvs
> /usr/repos), and make it group writable (chmod -R g+w /usr/repos).  (The -Rs
> are for 'recursive', so that ownership/permissions will also be changed on
> all subdirectories and files in the repository.)  Then edit /etc/group and
> add all the cvs-authorized users to the cvs group.  For your 4 users a, b, c,
> and d, you would find the line
> cvs:x:1005:
> (1005 is an arbitrary number; your group ID for cvs will proabably be
> different) and change it to
> cvs:x:1005:a,b,c,d
> If any of these users are logged in, they'll have to log out and back in
> before the change in group membership takes effect.
> > say a, b, c, d are four linux user on same linux
> > machine where cvs repository ( say repo1 )  is created. I want to provide a 
> > and
> > b  the access to the repo1 but not to c and d. Or I want to control module 
> > level
> > access for same repository. say m1, m2 are two modules in repository say 
> > repo2. a
> > and b should access repo2/m1 , b and c should access repo2/m2 and d should 
> > not
> > access any repository outside his userspace.
> Same basic techniques as above, except you would create a repo1 group owning
> the repo1 directory structure with a and b as its members, an m1 group also
> containing a and b, and an m2 group for b and c (with repo2/m1 owned my group
> m1 and repo2/m2 owned by group m2).
> If you're not familiar with groups and their uses in unix, you should read up
> on them.  They're very powerful and designed specifically to deal with the
> sort of situation you seem to be describing.
> --
> The Shortest Windows Manual:  "Turn off the power switch."
> Geek Code 3.1:  GCS d- s+: a- C++ UL++$ P+>+++ L++>++++ E- W--(++) N+ o+ !K
> w---$ O M- !V PS+ PE Y+ PGP t 5++ X+ R++ tv- b++ DI++++ D G e* h+ r++ y+

reply via email to

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