info-cvs
[Top][All Lists]
Advanced

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

RE: Ristricting access to CVSROOT....


From: Peter Connolly
Subject: RE: Ristricting access to CVSROOT....
Date: Thu, 15 Jul 2004 17:07:42 -0700

I enhanced the original contrib/cvs_acl:

    https://ccvs.cvshome.org/issues/show_bug.cgi?id=170

Although it's not yet part of the regular distribution, you may want to
take a look.

pc

> -----Original Message-----
> From: address@hidden 
> [mailto:address@hidden On 
> Behalf Of Mark D. Baushke
> Sent: Thursday, July 15, 2004 4:39 PM
> To: Hamid Ghassemi
> Cc: address@hidden
> Subject: Re: Ristricting access to CVSROOT.... 
> 
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hamid Ghassemi <address@hidden> writes:
> 
> > This may have been asked before; however, I cannot find the answer
> > anywhere.
> 
> See https://www.cvshome.org/docs/manual/cvs-1.11.17/cvs_18.html#SEC169
> https://ccvs.cvshome.org/source/browse/ccvs/contrib/cvs_acls.in
> https://ccvs.cvshome.org/source/browse/ccvs/contrib/cvs_acls.i
n?rev=HEAD

> We are trying to restrict access to CVSROOT directory such that only a
few
> can make changes to it and all other can checkout only to read.  How
can
> this be done?
 
Have the commitinfo script have an entry for CVSROOT which runs a
script. The script returns a zero exit code when $USER is in the allowed
list and a non-zero code when $USER is not in the list.

Look at contrib/cvs_acls in a tree where you built cvs 1.11.17 for ideas
or
https://ccvs.cvshome.org/source/browse/ccvs/contrib/cvs_acls.in?rev=HEAD

        -- Mark


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFA9xWw3x41pRYZE/gRAn/pAJ9KEaJZw3xoKcrLfEDe9nwyNPMiggCfYLeU
Duoi9VpHwMOa4kiu7XW1jtc=
=zRva
-----END PGP SIGNATURE-----


_______________________________________________
Info-cvs mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/info-cvs




reply via email to

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