SourceForge Services - CVS Repository

Your project has been issued its own CVS Repository, not just a directory on a master repository.

This means that your cvs logs, history files, and behavior are unique to your repository. This allows us to customize certain projects on request. The old method of housing several directories in one CVS tree also led to the mixing of log files and inability to separate certain parts of projects easily.

We've made custom changes to the CVS code to allow us to host this many CVS Repositories through one access point, and to clean up the handling of anonymous CVS users.

SSH Developer Access

The most common method of accessing CVS repositories remotely is through its "pserver" protocol implementation. This method is insecure, however, as it broadcasts passwords in plaintext over the net. It is possible to configure other methods of authentication through pserver, but not without considerable effort on the client side as well.

We have chosen to allow developers to access the CVS reponsitories through SSH, which the CVS client can easily do by setting one environment variable (and installing SSH).

While normally this would open up the CVS box to shell access, an in-house developed custom shell ensures that only SSH/CVS access is allowed.

[View SourceForge CVS Documentation]

Anonymous CVS Access

We open up the repositories for anonymous access through pserver. No passwords are sent in anonymous CVS access.

[Return to Site Service Documentation]