Reputation: 6990
I am using Eclipse Indigo RC4 with EGit (bundled). I have a project which I have committed to my local repository, and now I want to push from that to a remote repository I have in GitHub.
Pushing / Pulling from the command line tools works fine (I have configured RSA key based SSH authentication).
But when I try to push from EGit (via SSH pointed to GitHub), I get a prompt to enter my pass phrase. But when I enter the correct pass phrase, it prompts again for the same (note: username appears as git because that's the default when using GitHub. I guess that wouldn't be a issue).
Under Eclipse preferences, I have double checked to ensure that it is configured to use the RSA tokens I have generated.
Upvotes: 23
Views: 8492
Reputation: 6990
Got it sorted out by following this link http://www.eclipse.org/forums/index.php/t/197428/.
I created an environment variable GIT_SSH
which points to /usr/bin/ssh
(which was the SSH implementation I was using in command line) and started Eclipse. When this environment variable was present, Eclipse connected using my shell's SSH tool and there was no prompt for pass phrase and it worked fine.
Upvotes: 22
Reputation: 361
On Eclipse Juno, Jsch is already > 1.44 and yet the problem still happens (for me). I also tried setting GIT_SSH and this didn't work either. My previous keys had been generated by ssh-keygen, I can only guess that this doesn't generate a suitable key.
What I did that worked was this:
Use Eclipse to generate a new DSA key - creating a 1024 bit key Eclipse->Preferences->General->Network Connections->SSH2->Key Management
[It might work with RSA I didn't try]
Copy the generated public key to the remote repo
Click the [Save Private Key] button without entering a passphrase
RESTART ECLIPSE
Eclipse/EGit will now synch with the remote Git Repo, without requiring a passphrase - phew!
Upvotes: 2
Reputation: 3454
Even simpler is to update the JSch bundle to 0.1.44 from eclipse orbit repository (p2 software site): http://download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/repository/
The underlying problem is actually that JSch < 0.1.44 does not support the newer encryption scheme AES-128:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=326526
Upvotes: 13