Install cvs in a different place than the version you are using.
Make a script named cvs in the current location of cvs. That script should check the cvs commands vs. valid users. If everything is OK, then it should invoke the new cvs in the new place with the arguments passed to it.
This won't protect you from truly malicious developers who invoke cvs directly from the new location, but you probably have already fired those people from your project. :-)
Fred
David Leskovac wrote:
[I sent this msg 10 days ago & noone responded. So, I'm trying again.]
Hello,
We are currently using an ancient version of CVS (1.11.1p1) on a rather old Linux server (Red Hat 6). I intend to upgrade to CVS 1.11.19 & eventually upgrade the Linux OS. In the course of our CVS upgrade discussion we started discussing how to increase security with regards to CVS access. I am aware of the cvsacls script that provides fairly fine-grained permissions to do check-ins but is there also a way of restricting who is allowed to do certain cvs commands? In particular, we would like to restrict who can create/delete tags & branch tags. Is it possible to restrict 'cvs tag' & 'cvs rtag' on a user or group level?
Thanks, -Dave
_______________________________________________ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
-- Frederic W. Brehm, Sarnoff Corporation, http://www.sarnoff.com/
_______________________________________________ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs