Cvs linux pserver not validating password
This is done by adding the name of the system account you want the cvs account to run as at the end of the line (use "cvs" for Now set up a user group called cvs or some such and add your users to this group.Give this group permission to write to the /home/cvs/cvsroot directory and all subdirectories. CVSD allows running a repository which has been chroot'ed. Under this scheme, you will be running the invocation of CVS as root, so this extra bit of security will help.If you don't currently have a repository to bring over you will have to create one with this command which will create a default empty repository at the path specified.When you add a user cvs doesn't know that there is already a user on the system with that name.
As things change you will probably want to change this. Depending on what you are intending to do with CVS depends a little on which tools you will want to use on the client side to interact with your repository.If "pserver" is a special mode, then I assume there is a default mode as well. Now there is the all important CVSROOT, that is a directory used to store cvs archives e.g.export CVSROOT=/usr/local/cvsroot Because of the client-server architecture this CVSROOT can be situated at a different machine and you need to have an account on that machine to access it: export CVSROOT=:sparc:/usr/local/cvsroot You're prompted for a user name and a password, for :[email protected]: only for a password. In practical situation (like with a dedicated cvs-server) you don't want user accounts for the server with access to cvs-files.CVS allows you to add users independently of the underlying OS installation which is both a good thing and a bad thing.Probably the easiest way from a management point of view is to use the Linux users for CVS as well although this does have a few minor security issues since this is just a home network we will grin and bear it.