CVS SecurityThere are several ways to make a CVS connection across a network while providing a high level of resistance to security attacks:
To access CVS through a firewall depends on the firewall and security policies in place. Typically, you will supply an rsh replacement which makes the connection. There are a large variety of network security schemes and setups out there. If terms like SASL, SOCKS and the like mean anything to you, and you want to know whether anyone is working on supporting them for CVS, see the Information Page on Networking. For controlling access once users have made it past the network, CVS features like the "cvsadmin" group and the commitinfo administrative file may help (see the Cederqvist for information on those, or the Information Page on Access Control). In particular, take a look at what that page has to say about exactly what kinds of protection each feature provides (or does not provide). Some aspects of CVS security are discussed in the Cederqvist manual. For more information on getting this manual, see our Cederqvist manual page. Non-CVS-specific computer security information
Other information on CVS securityWhether this is best for you depends on your own security policies and preferences, but one popular technique is to run the CVS server in a chroot'd environment. For details see the pages from OpenBSD, Samba, or Chris Black. If you are running pserver, there are a variety of tools for manipulating the encrypted passwords in CVSROOT/passwd, but cvspwd from GlassFish is one of them. Tim TimeWaster's page about how to set up CVS via SSH, and give people access to CVS and not login access on the machine (note: this is subject to the usual disclaimers about how giving people read/write access to CVS does allow them to circumvent any measures designed to prevent them from executing arbitrary commands on the server). We expect to update this page with future CVS security announcements as they are made. |
![[ Valid XHTML 1.0! ]](/branding/w3c-valid-xhtml10-44x16.png)
![[ Valid CSS! ]](/branding/w3c-valid-css-44x16.png)
