Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 334926 - EGit asks me for password even when public key is used
Summary: EGit asks me for password even when public key is used
Status: RESOLVED INVALID
Alias: None
Product: EGit
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-20 12:01 EST by Tomasz Zarna CLA
Modified: 2011-01-21 05:38 EST (History)
0 users

See Also:


Attachments
Cloning in msysgit (2.58 KB, image/png)
2011-01-20 12:02 EST, Tomasz Zarna CLA
no flags Details
Cloning in EGit (24.15 KB, image/png)
2011-01-20 12:03 EST, Tomasz Zarna CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tomasz Zarna CLA 2011-01-20 12:01:34 EST
JGit+EGit 0.11.0.201101140331

I'm under Windows, running cygwin with ssh daemon. I've uploaded my public key to .ssh, so each time I do "git clone ssh://..." in msysgit I'm asked to enter a passphrase for the key. This is fine, but when I enter the same URI in EGit I'm asked for my password (not the passphrase).

Does git honor authentication methods order from "Network connections > SSH2 > Authentication Methods (tab)"? iiuc, the situation described above could happen only when the "publickey" method had been manually set as less preferred than "password".

Is it related to bug 326526?
Comment 1 Tomasz Zarna CLA 2011-01-20 12:02:50 EST
Created attachment 187213 [details]
Cloning in msysgit
Comment 2 Tomasz Zarna CLA 2011-01-20 12:03:16 EST
Created attachment 187214 [details]
Cloning in EGit
Comment 3 Tomasz Zarna CLA 2011-01-21 05:38:28 EST
I had SSH2 home set to "$HOME/ssh", which was empty. After resetting the preference to "$HOME/.ssh", where my private key actually is, EGit asked me for the passphrase.

The ssh/.ssh issue (bug 294925) may be really confusing. Marking this one as invalid.