On Tue, 2005-09-13 at 09:16 -0400, Roberto C. Sanchez wrote:
> How exactly did you get this to work? I am running Eclipse on Debian
> Stable and I can't get it to work with the ssh-agent. I have emailed
> the list previously trying to find out what is wrong, but it wasn't
> until last night that I figured out what was going on:
I used to have a script that has user name and passphrase as parameters
but, as you can imagine I was deeply unhappy about it. One day I failed
to use my script and just invoked Eclipse directly and didn't notice
there was a problem until later. I then removed all the scripts (with
great satisfaction:-) and have never had a problem. Well until the
upgrade to 0.9.33 and now I need to say where my private key file is
which I didn't used to have to do.
So all in all... I haven't a clue.
I use the standard Gnome login which invokes ssh-agent before starting
the primary bash so all subsequent programs inherit access to
ssh-agent.
[ ... password bit not relevant ... ]
> - If I specify only the path to the private key (either in the
> ~/.eclipse/org.eclipse.platform_3.1.0/configuration/config.ini file or
> on the command line), then I get "Authentication Cancelled" without
> any evidence of a connection to the server.
> - If I specify both the path to the key and the passphrase (either in
> the file or on the command line), then it works and the auth.log on
> the server shows "Accepted public key."
I just updated and there was an SSH activity even though I never specify
passphrase (and yes I am certain that my private key has a
passphrase :-)
> I would really like to know how to get this working with ssh-agent, as
> every other application that needs access to the ssh keys works fine
> with ssh-agent. Particularly, I am uncomfortable with leaving my
> passphrase specified in the configuration file. I also certainly don't
> want to specify it on the command line, as anyone logged into the
> machine when I have done that can run a `ps aux` and see my passprase.
I am at a loss, it just works.
> I am not sure if this anything to do with it, but I use keychain to
> handle my ssh-agent and gpg-agent. So, access to the ssh-agent is via
> the environment variables SSH_AGENT_PID and SSH_AUTH_SOCK. Also, on my
> system, ssh-agent is not a parent of any of the processes of my login
> session. That is, my pstree looks like this:
>
> ssh-agent (rooted by itself)
>
> sh --> WindowMaker --> WindowMaker --> elcipse --> eclipse
> |-> firefox-bin
> |-> gnome-terminal
> |-> (various WMaker dockapps)
>
> Any ideas?
Perhaps that is the point, ssh-agent is the root of all my processes
with currently
SSH_AGENT_PID=4469
SSH_AUTH_SOCK=/tmp/ssh-SXeeJm4407/agent.4407
SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
the environment associated with every process I spawn.
> Maybe it would be possible to get future versions of Subclipse to check
> for and honor the SSH_AGENT_PID and SSH_AUTH_SOCK environement
> variables.
I think they already must.
--
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 00:27:02 2005