Hi!
I tried to use svn+ssh protocol on Windows. I installed OpenSSH on the
server, then followed install instructions, and succeeded to start the
server. I tried to login from another machine with ssh, and that was OK.
I tried to access the svn repository remotely with "svn log
svn+ssh://machine/path" and encountered a lot of problems:
- svn client said that it can't find the executable. But didn't said
which executable.
The problem was the ssh client was not on the PATH.
The solution was to put it into the PATH.
- Svn client said "svn: Connection closed unexpectedly"
The problem was the server was configured by default to send a
Banner to the client before asking for password.
The solution was to edit the OpenSSH\etc\sshd_config file to
disable sendig banner text.
- Svn client asked for password and then Svn client said "svn:
Connection closed unexpectedly" again.
The problem was the ssh server couldn't find the user's home
directory and sent an error message about it.
The solution was to edit the OpenSSH/etc/passwd file and
modifying all users' home directory to an existent one.
And voila: the log command succeeded!
I wrote it to help other users to setup svn+ssh on Windows and to note
that this protocol is very fragile and svn error messages could be very
cryptic. Maybe if the svn clinet gets some unexpected text under logging
in it should echo it to the standard error and then ignore it. And when
it can't find an executable it would be helpful what is the problematic
command string.
Is it possible to fix these weaknesses?
Despite these problems I like svn, and I hope my comments help to build
an even better svn:
Gyula
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 24 18:08:41 2005