cvs -d :pserver:bach@chainsaw.brickyard.com:/usr/local/cvsroot login
cvs -d :pserver:bach@chainsaw.brickyard.com:/usr/local/cvsroot login
cvs -d :pserver:bach@chainsaw.brickyard.com:/usr/local/cvsroot checkout foo
The `:pserver:' is necessary because without it, CVS will assume it should use rsh to connect with the server
http://turbulence.ucsd.edu/~hxluo/tutorial/cvstour.html#ssh
This is easier for the administrator because he/she doesn't have to do anything for the server once the repository is created. The clients need to have UNIX accounts on the server machine and be able to connect to the sever using SSH. To access the repository using SSH, do this first:
%setenv CVSROOT :ext:$USER@turbulence.ucsd.edu:/usr/local/newrepository %setenv CVS_RSH ssh
Then you don't need run 'cvs login', but run CVS commands directly. The shell will ask for the password for your account automatically.
http://cvsbook.red-bean.com/cvsbook.html#Anonymous_Access http://www.gigascale.org/softdevel/faq/16.html
If you list a username in CVSROOT/writers, that user will have write access, and every pserver user not listed in writers will have read-only access (that is, if the writers file exists at all, it implies read-only access for all those not listed in it). If the same username is listed in both files, CVS resolves the conflict in the more conservative way: the user will have read-only access.
The format of the files is very simple: one user per line (don't forget to put a newline after the last user). Note that the files apply to CVS usernames, not system usernames. If you use user aliasing in the CVSROOT/passwd file (putting a system username after a second colon), the leftmost username is the one to list in a readers or writers file.
Put this in CVSROOT/writers:
anonymous
To generate an encrypted password, run cryptout.pl with the password
gigasource:root: %C2> /usr/local/bin/cryptout.pl foobar oPG6N3As668O2 gigasource:root: %C2>
and then placing that encrypted password in a new password entry in $CVSROOT/CVSROOT/passwd
Another way to create this file is to use htpasswd, which is normally used to generate Apache access password files. The format it creates is about the same as that which CVS requires, except for the :cvsuser appendage to each line. You'll still have to do that manually, but it allows you to create a passwd file with passwords different that those in the regular /etc/passwd file.
$ htpasswd -b passwd anonymous '' Updating password for user anonymous
Modify your copy of CVSROOT/config so that its contents look like this:
# Set this to "no" if pserver shouldn't check system users/passwords SystemAuth=no
Newsgroups: fa.info-cvs Date: 2001-09-29 12:27:29 PST
I've got a stange error message with cvs. How did I install it: I installed it with apt-get from my Debian.
/etc/inetd.conf:
cvspserver stream tcp nowait.400 root /usr/sbin/tcpd /usr/sbin/cvs-pserver --allow-root=/var/lib/cvs
ls -l /var/lib
drwxrwsr-x 3 root src 4096 Sep 29 20:15 cvs
cat /var/lib/cvs/CVSROOT/passwd
fly:$1$dQ8SdJoA$6jNn5PLEfCfNq3/7jFeV90:cvsuser
cat /var/lib/cvs/CVSROOT/writers
fly
export of the user fly:
export CVSROOT=:pserver:fly@ostium:/var/lib/cvs
The user fly can login without any troubles but when I do:
cvs import -m "Management Clients Companies project" mcc ostium start
I 've got an error message:
Fatal error, aborting. cvsuser: no such user
I do have a hunch that the passwd file above is describing that when the cvsuser "fly" logs into cvs, then cvs should change userid to the system user "cvsuser", which doesn't exist in /etc/passwd. Try adding the user cvsuser in /etc/passwd, or use the "adduser" command to add the user.
Newsgroups: fa.info-cvs Date: 2001-06-15 14:18:49 PST
I have been trying to setup a chroot cvs server for a while now, but keep running into the same problem. I have created a user cvs to run the server under, and have chroot'd the server to /home/cvs/jail/
i have followed the instructions in a few howtos on setting up a Chroot CVS Server, but always run into this problem:
I am able to login and authenticate with the pserver alright, but when I try to import a new project into the respository I get :
[rae@skywalker myproj]$ cvs -d $CVSROOT import myproj v1 r1 Fatal error, aborting. cvs: no such user cvs import: authorization failed: server vader rejected access to /cvsroot for user rob
The respository is setup in /home/cvs/jail/cvsroot
the CVSROOT/passwd file contains:
rob::cvs billy::cvs susy::cvs
the CVSROOT/readers file contains:
susy
the CVSROOT/writers file contains:
rob billy
(Just using sample names )
But each time I get the no such user error.
I have gone seaching though the cvs-info mailing list archive, and found no other mention of this problem. I am curious though, is a chroot jail necessary? In one thread about the chroot patch for 1.10, someone posted that it was easy for a malicious user to execute a script and escape from the chroot jail, which makes me wonder what is the point then of a chroot jail?
> cvs: no such user
Please read the sections of the manual on setting up a CVS server, connecting to a server, and possibly "Trouble connecting to a CVS server" in the "Troubleshoting" section. There is a manual available online at http://cvshome.org/docs/manual .
It looks like you didn't log in or logged in with an invlaid password.
Derek
Newsgroups: fa.info-cvs Date: 2001-09-06 08:46:41 PST
I have my cvs server running on a linux box and am using pserver mode to connect. When I have the CVSROOT/config file set SystemAuth=yes then cvs -d :pserver:user@hostname:/myrepos login works and I can log in using username and the system password for username.
I then used passwd command to change the password to something else and cut and paste the new password field into the CVSROOT/config file
e.g.
username:sB3A79YDX5l4s
I also set SystemAuth=no
And then did a commit on both config and passwd (after adding passwd).
When trying to log on I now get:
"no such user username in CVSROOT/passwd cvs login: authorization failed: server homenet.net rejected access to /myrepos for user username"
If I view the passwd file directly under the CVSROOT directory then I can see username. I have also tried setting passwd file as: username: as one would do for anonymous users, but same result.
At all times I used edit and commit to make changes to file.
I'm trying to set up anonymous access for a repository. I've created a passwd-file with a user anon, a readers file that contains that user (and a newline), and added them to the repository. When I try to access it through
cvs -t -d :pserver:anon@host:/usr/home/cvsadmin/repository login
I am prompted to enter my password, but I only get
Fatal error, aborting. anon: no such user cvs [login aborted]: authorization failed: server swt rejected access
When I change SystemAuth to no, I get:
CVS password: no such user anon in CVSROOT/passwd cvs [login aborted]: authorization failed: server swt rejected access
bash-2.03$ cat passwd anon:/1kgJapGxEYM2:cvsadmin
But the user is there !
Where's the problem ?
Strange enough, in the the $CVSROOT/CVSROOT-directory, there is no real passwd-file, just a passwd,v-file. All the other files have real-files associated with their RCS-relatives.
> And then did a commit on both config and passwd (after adding passwd).
passwd is usually edited in place rather than being maintained with CVS for security reasons. If you're sure you want to maintain it with CVS, you need to add it to CVSROOT/checkoutlist so that it gets updated when committed.