Hello Dan,
Thank you very much for sharing your ideas on what my be the reason of the
problem reported. I would like to add a single correction (unrelated to the
problem):
> 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.
>From version 0.9.3 (Subclipse 0.9.35), JavaSVN uses Ganymed SSH library
instead of JSCH (http://www.ganymed.ethz.ch/ssh2/).
Ganymed is not only more reliable, but also features much more clear source
code and design, comparing to JSCH. Ganymed author, Christian Plattner, also
provided me with the excellent level of support when I had number of
SSH-related questions.
Ganymed implements more or less the same features as JSCH (at least from
JavaSVN point of view, as far as I understood there are number of
SSH-specific features unique to Ganymed), so it does not support PPK key
format as well as JSCH and JavaSVN users have to use private keys in OpenSSH
format as you correctly noticed.
So, if anyone works with SSH connections in Java and not satisfied with JSCH
(as was me) I could recommend to take a look at Ganymed library (as I did
:)).
Alexander Kitaev,
TMate Software,
http://tmate.org/
http://jetbrains.com/tmate/
> -----Original Message-----
> From: Dan North [mailto:dan@tastapod.com]
> Sent: Tuesday, November 01, 2005 20:24
> To: users@subclipse.tigris.org
> Subject: Re: ssh implementation is bogus
>
> 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.
>
> hth,
> Dan
>
> 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:
>
> >Hi,
> >
> >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
> >org.tmatesoft.svn-0.8.7.tar.gz.
> >
> >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
> >
> >Regards,
> >jens.
> >
> >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
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
>
>
Received on Wed Nov 2 10:51:09 2005