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

Re: Subclipse 0.9.33 Released

From: Roberto C. Sanchez <roberto_at_familiasanchez.net>
Date: 2005-09-13 19:50:00 CEST

On Tue, Sep 13, 2005 at 01:28:35PM -0400, Mark Phippard wrote:
> I just cannot envision how JSch could interact with ssh-agent. My
> assumption is that either Russel's key does not require a passphrase, or
> JavaSVN has cached his passphrase from some earlier time when he was using
> JavaSVN.

True. In my case, I though I had it working at one point. However,
what had happened was that I had placed my passphrase in the config.ini
under ~/.eclipse. Once I had done that, subversion had cached it in
~/.subversion/auth/svn.ssh, causing later attempts without me directly
entering the passphrase appear to succeed. In fact, it had been using
the cached credentials. Once I removed ~/.subversion/auth/svn.ssh, it
want back to the behavior we have been observing all along, where it
can't get to the key.

In any event, I think that your point is valid and probably should be
brought up to the JSch developers. I will email them and see what they

I also did a bit of experimenting with Eclipse's CVS module. What ended
up happening was that even when launched eclipse via ssh-agent:

ssh-agent eclipse

It still didn't work. I added the key, yet to connect to a cvs server
via extssh, Eclipse still wanted me to enter the passphrase. That
certainly reinforces your thoughts on JSch simply not communicating with
the ssh-agent.


Roberto C. Sanchez

  • application/pgp-signature attachment: stored
Received on Wed Sep 14 03:50:00 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.