Setting up the password authentication server

Please note that the network part of CVS has been mostly rewritten and redesigned with the following design goals:

• security; CVS server now consists of several separate programs: first one simply gets username and password; another one authenticates and authorizes the user and then runs the CVS-server itself which works with the repository. As a result, security-critical parts of code became very short, clean, understandable and auditable;
• compatibility; there is a lot of various CVS clients around the world; complete compatibility has been preserved; your server machine gets additional security while your users work as they always worked;
• virtual CVS repositories support; every repository you are hosting needs only one (maybe two) system accounts while it can have as many virtual users as needed;
• ease of administration in virtual repositories case; there is now long-awaited command `cvs passwd' which you can use (remotely or locally) to add, remove or change information about users; also, your users can change their passwords for themselves, remotely or locally;
• additional flexibility even when using system accounts for authentication (without virtual repositories); authentication program is now completely separate so it can do whatever you want. It can e. g. use PAM (Pluggable Authentication Modules), consult SQL-server or do whatever else you wish.

Go to the first, previous, next, last section, table of contents.