[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: ssh implementation is bogus

From: Dan North <dan_at_tastapod.com>
Date: 2005-11-01 20:23:56 CET

The showstopper for me with svn+ssh over javasvn was having a different
username on the server. The remarkably responsive Alex has resolved this
so I expect the next subclipse plugin release to have the fix in it.

Note that the java ssh implementation that Alex uses - jsch - only
understands openssh private key files, so your putty .PPK file won't
work. You can convert a Putty secret secret key into an openssh key
using the puttygen utility.

Once you get javasvn working you will find it is quicker than using
svn+ssh over the command line client because it maintains a persistent
ssh connection so it doesn't need to do the ssh handshaking every time
you do anything.


ps. Password access might be disabled on your ssh server - it's a
configurable option in the sshd config and is often disabled as a
security measure.

elkner@linofee.org wrote:

>unfortunately the svn+ssh via JavaSVN is bogus. It is not possible
>to connect to a svn+ssh repository - neither using a password nor private
>key authentication. The only option, which seems to work, is using the
>commandline interface :(.
>The last version, which worked for me, was subclipse-0.9.28.tar.gz with
>At the moment I've installed site.0.9.36.zip on eclipse 3.1.1/Linux.
>Subversion server/client are version 1.2.1
>PS: In case you need more info, send me a Cc:, since I'm not at this list.
>To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
>For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Wed Nov 2 06:23:56 2005

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.