Mainly the problem seems to be getting a ssh client to work right.
First a few things about my setup. The client is running NT4SP6.
The server is running a mongrel UNIX.
I've setup svnserve to run from inetd and managed to get it to respond
to the svn:// protocol properly.
For the moment I've replaced the svnserve program with a bash script
which prints out to a temporary file the command line arguments.
That way i can see when it is actually called. I see so far that
svnserve has not been called.
Let us begin with the standard ssh from openssh.
The problem with ssh is that you cannot specifiy
the password on the command line. I have to
use the environmental variable SVN_SSH, otherwise
it tried to log me in as Administrator, and there is
no such account on the server. I specify the user
in SVN_SSH. So the SVN_SSH looks like SVN_SSH="ssh -l root".
Now some general commentts. My repository is in /svn. I won't
broadcast the IP of my server ( in case hackers both read this
and somehow break into my LAN ), but will reffer to it as #IP.
I use the dotted version ( 184.108.40.206 ) to eliminate the possibility of
DNS errors confusing the issue. I have stored a prohject test in the
repository. To test the setup, I use the command:
>svn checkout svn+ssh://#IP/svn
I have also tested the command:
>svn checkout svn://#IP/svn
Before using a particular SVN_SSH, say SVN_SSH="xyz", I try to
execute the following two commands:
xyz #IP svnserve
to make sure the format is correct. I don't use a particular SVN_SSH
unless it passes this test. I try it in both cygwin bash and a "DOS"
Back to particular cases:
SVN_SSH=" ssh -l root"
the openssh version of ssh, just causes (1)
Checking my Linux logs, Ifind the message for sshd:
fatal: Timeout before Authentication for #ip.
I can't specify the password in SVN_SSH because
ssh has no commandline option for password, but
ZoneAlarm does ask for permission for ssh ( ZoneAlarm
is a firewall ).
I try TortoisePlink because some archive say to use it.
It fails to work, but also fails my tests popping up a dialog
box saying "Cannot write to standard output".
Next are putty, plink and the following four SVN_SSH
SVN_SSH="path/putty.exe -ssh -l root -pw password "
SVN_SSH="./putty.exe -ssh -l root -pw password "
SVN_SSH="path/plink.exe -l root -pw password "
SVN_SSH="./putty.exe -l root -pw password "
The results for putty, iot passes the login test, but fails the test
to send svnserve to the server. I try it anyway and get the message:
svn: The system cannot find the file specified.
svn: Could not create tunnel.
With plink.exe both tests succeed, but I get the same message.
In both cases ZoneAlarm does not ask for permission to connect,
and the temporary file accessed by the script is not created.
Now a final request. Before you post a suggestion read the whole
post and make sure that you are not suggeting that I have already
suggested. ( Hey I didn't put in a lot of time writing this only to
have you blow off most of it. )
If you need any clarification feel free to ask.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Dec 17 15:19:16 2003