Eclipse Community Forums: EGit / JGit » Force using JSch instead of TortoisePlink on Windows ?

Help

Home

Home » Eclipse Projects » EGit / JGit » Force using JSch instead of TortoisePlink on Windows ?

Show: Today's Messages :: Show Polls :: Message Navigator

Force using JSch instead of TortoisePlink on Windows ? [message #976620]

Thu, 08 November 2012 18:24

Martin Oberhuber

Messages: 1007
Registered: July 2009

Senior Member

Hi all,

I've just jumped through some hoops getting Egit to work with ssh protocol against Eclipse Gerrit (which forces publickey authentication).

Turned out that Egit insisted on using TortoisePlink since I also had TortoiseGit and Msysgit installed - and the private keys that I had set up in Eclipse were not used at all. Details here:
http://wiki.eclipse.org/TM/Git_Workflows#Windows_Install

While using TortoisePlink and Pageant makes sense once it is configured, it's also somewhat unexpected and I'm wondering (a) why EGit inists on picking up TortoisePlink and (b) how I could force it to use the internal JSch ?

Thanks,
martin

Report message to a moderator

Re: Force using JSch instead of TortoisePlink on Windows ? [message #976629 is a reply to message #976620]

Thu, 08 November 2012 18:30

Martin Oberhuber

Messages: 1007
Registered: July 2009

Senior Member

I should probably add that in my Msysgit Git Bash, I have this:

mober@SZG-MOBER-L3 ~
$ env | grep -i git
GIT_SSH=C:\Program Files\TortoiseGit\bin\TortoisePlink.exe
PWD=/d/Workspaces/git
SVN_SSH=C:\Program Files\TortoiseGit\bin\TortoisePlink.exe
HOME=/d/Workspaces/git
!D:=D:\Workspaces\git
GNUPGHOME=/d/Workspaces/git/.gnupg
HISTFILE=/d/Workspaces/git/.bash_history

Which is already somewhat confusing since ssh-keygen and ssh use a different ssh than git so "git clone ssh:..." may fail while sanity checking ssh by itself may work.

I'm not sure whether that is a default setting or how I got to that setup ... maybe because I had set up TortoiseSVN + Putty + Pageant at some time in the past for Subversive / Subclipse (which also required jumping through hoops, even harder than the git ones at that time).

Report message to a moderator