On Tue, 2005-09-13 at 13:01 -0400, Roberto C. Sanchez wrote:
> a) Russel made it happen, so it must be possible
> b) I know how to setup my environment, but somehting is still wrong
> c) Russel and I have sufficiently similar configurations that I can't be
> that far off as it is.
Curiouser and curiouser. Applying jsch and ssh-agent to Google leads to
an email from Atsuhiko Yamanaka:
If you ask the possibility that "jsch can communicate with
ssh-agent program?", we will not be able to do. The ssh-agent
program depends on unix-domain sockets and we can not handle
them in pure java.
So it seems Java cannot access ssh-agent -- unless the situation between
Java and UNIX domain sockets has changed since last year. I suspect
not. Therefore that is not is what is happening. Unless something very
weird is happening.
I have even less idea how things happen now. I have three private SSH
keys: a Protocol 2 DSA key with passphrase; a Protocol 1 RSA key with
passphrase and a special purpose Protocol 2 DSA key with no passphrase.
My server does not allow Protocol 1 access and I am specifying the key
with a passphrase.
I start Eclipse with:
|> /opt/eclipse-3.1/eclipse -vmargs
-Djavasvn.ssh2.key=/home/users/russel/.ssh/id_dsa
and get the following on the console:
Failed to load JavaHL Library.
These are the errors that were encountered:
no libsvnjavahl-1 in java.library.path
no svnjavahl-1 in java.library.path
no svnjavahl in java.library.path
java.library.path = /usr/lib/j2sdk1.5-sun/jre/lib/i386/client:/usr/lib/j2sdk1.5-sun/jre/lib/i386:/usr/lib/j2sdk1.5-sun/jre/../lib/i386:/home/users/russel/build/lib
As soon as I attempt an access of a Subversion store either via update
in Java perspective or accessing any of the stores in Subversion
perspective there is an SSH transaction and I get the following
in /var/log/auth.log on the server:
Sep 13 19:21:04 dimen sshd[2811]: Accepted publickey for russel from ::ffff:192.168.1.3 port 48046 ssh2
Sep 13 19:21:04 dimen sshd[2813]: (pam_unix) session opened for user russel by (uid=0)
This means that whatever SSH system is being used by Eclipse/Subclipse
it has either found a way around requiring the passphrase or it is
getting authorization somehow to use the key even though
Eclipse/Subclipse has never asked for a passphrase.
We have now reached the end of my knowledge and experience. However if
there are some experiments I can undertake -- short of changing keys or
passphrases then I am willing to try.
--
Russel.
====================================================
Dr Russel Winder +44 20 7585 2200
41 Buckmaster Road +44 7770 465 077
London SW11 1EN, UK russel@russel.org.uk
Received on Wed Sep 14 04:29:07 2005