Mike Castle wrote:
> On Fri, Oct 13, 2000 at 02:42:15PM +1100, Luke Kendall wrote:
> > But the CVS archive isn't working for the Windows machines anymore;
> > any attempt to do a cvs login gets the error below:
> >
> > CVSROOT set to :pserver:luke@localhost:/home/mantovani/cvs-archive
> > Started ssh, so now you need to cvs login:
> > (Logging in to luke@localhost)
> > CVS password:
> > cvs [login aborted]: authorization failed: server localhost rejected access
>
> Wait. You are using ssh to log back into the Windows machine?
> (luke@localhost) That doesn't seem to make a lot of sense. Or were you
> just obscurring information there?
No, that's exactly what I used; it's the output from a script wrapped
around it that only starts an ssh connection to the cvs server machine
if there isn't already one running, and also sets some environment
variables.
Fundamentally it does this:
wterm sh -c "ssh -l $LOGNAME -L 2401:localhost:2401 mantovani" &
CVSROOT=":pserver:$LOGNAME@localhost:/home/mantovani/cvs-archive"
CVS_SERVER="/usr/bin/cvs" export CVS_SERVER
cvs login
This means that at localhost on the client, and on localhost on the
server, an ssh connection to port 2401 is made. So all cvs communications
are sent via ssh. We use this because we're working on a clean room
project; it just happens to be the same system we use if working off
site.
> Why don't you use :ext:luke@linuxhost:/home/mantovani/cvs-archive
>
> And set CVS_RSH to ssh.
See above. Plus, it used
to work until we changed the CVS server from one Linux machine to
another. And this way still works when talking to another server
serving another CVS archive.
A very significant fact: when logged into the cvs server, if we use
CVSROOT=":pserver:$LOGNAME@localhost:/home/mantovani/cvs-archive"
cvs login fails there! Doing a trace of it, all we see is the
server sending the message "I HATE YOU". So the password validation
appears to be failing.
In summary: I think we're using ssh for good reasons; it used to work;
changing from one Linux machine to another (and re-doing the config)
stopped it working; we can still use the technique to talk to another
server serving another CVS archive.
Any hints about how we diagnose this? Does cvs provide any verbose
logging or debug mode? AFAIK, cvs login takes no options.
My next step otherwise will be to modify the cvs source to generate
some information to trace what's going on.
luke
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
