This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Problem with 'cvs login'
- From: Brian Dessent <brian at dessent dot net>
- To: "'cygwin at cygwin dot com'" <cygwin at cygwin dot com>
- Date: Tue, 26 Apr 2005 16:03:00 -0700
- Subject: Re: Problem with 'cvs login'
- Organization: My own little world...
- References: <959DF48BD1458D4C8DBFDAC8DF80D7F701D500A2@europa.ats.sensis.com>
- Reply-to: cygwin at cygwin dot com
"Rancier, Jeff" wrote:
>
> I want to provide access to the respository remotely and for other users.
> No, while reading the FAQ, I was under the impression it would be created
> the first time, just use mkpasswd? Didn't know all that, that's for the
> info.
If you are providing write (commit) access then you should not use
pserver, it sends passwords in plaintext. Use ssh. It's even simpler
to setup because sshd uses the built in windows user accounts, whereas
CVS pserver requires you to maintain a seperate set of accounts.
I think you're confusing the two passwd files. One is /etc/passwd which
is created by the Cygwin command mkpassd, and should be created
automatically when you first log on after installing Cygwin. This is the
standard unix passwd file and is used by many commands.
The CVS passwd file is $CVSROOT/CVSROOT/passwd and is a completely
different file, with a different format, that is only used by CVS. You
must create and maintain this file yourself. Section 2.9.4.1 of the CVS
manual tells you all about this.
Brian
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/