HI Marting,
Thanks for you comment. However I'm not sure if I understand what you're
saying (my unix knowledge is not much more then ls -l :).
What I'm trying to prevent is that people who can access cvs cannot create new
modules unless they are listed in the avail file. The current setup is that
everybody can write into cvs and that security is arranged by the avail file.
regards,
janco
Infoman: Martin Kretschmar wrote:
> Hi,
>
> CVS is a non-suid program, so the normal file access
> permissions apply. The normal file protections would
> be something like "rw-r-r--" or "rw-r-----", depend-
> ing on wether you want an access by anybody else or
> not. The directories should have "rwxrwx-r-x" or
> "rwxrwx----" and an additional "g+s", so that new
> files inherit what they need.
>
> Note that even with checkout, CVS will write locks
> into the CVS directory tree. So in oder to allow
> non group owners to checkout, a different "LockDir"
> has to be specified in the CVSROOT/config file.
>
> Regards,
> Martin
>
> ----- Original Message -----
> From: "Janco Tanis" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, May 14, 2001 2:59 PM
> Subject: import and cvs_acl
>
> > Hi, I'm using the cvs_acl perl script to set commit permissions on
> > modules within the repository. This works fine however it is possible
> > for people who can access the repository that they can import without
> > any checks of the cvs_acl script. How can I setup cvs that it checks for
> > access also on an import?
> >
> > regards,
> > --
> > Janco Tanis
> >
> > ------------------------------------------------------------
> > COAS, Your partner in computer aided services
> >
> > Nijverheidsweg 34 Tel: +31 (0) 187 49 3222
> > Postbus 44 Fax: +31 (0) 187 49 2912
> > 3250 AA Stellendam Email: [EMAIL PROTECTED]
>
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
