| Summary: | Push/clone to/from ssh git repo (public key authentication) fails if usernames mismatch | ||
|---|---|---|---|
| Product: | [Technology] EGit | Reporter: | Severin Gehwolf <sgehwolf> |
| Component: | Core | Assignee: | Christian Halstrick <christian.halstrick> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | sgehwolf, stefan.lay |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Severin Gehwolf
Are you sure that Eclipse SSH supports asks you for a password to "unlock the SSH key"? I see quite often that users are asked for passwords because eclipse does not pick the expected ssh keys. And if eclipse uses wrong ssh keys and fails to authenticate to the host it falls back to standard authentication which is by password. Have you checked in eclipse ssh preferences that the right ssh keys are configured? Chris, this problem isn't happening for me anymore. I don't quite remember exactly what I did wrong, but it may be that I simply entering the wrong passphrase for my SSH key (which Eclipse tried to unlock). The username showing up when prompting for an SSH key passphrase is confusing nevertheless. Not sure if that's an egit problem or of the SSH eclipse plugin. Thanks for your response, though. (In reply to comment #1) > Are you sure that Eclipse SSH supports asks you for a password to "unlock the > SSH key"? Yes, Eclipse asks for the passphrase of the SSH key (id_rsa in my case). > I see quite often that users are asked for passwords because eclipse > does not pick the expected ssh keys. And if eclipse uses wrong ssh keys and > fails to authenticate to the host it falls back to standard authentication > which is by password. That may have happened for me at some point, because I was confused by the filled in username. > Have you checked in eclipse ssh preferences that the right ssh keys are > configured? Yes, it was configured correctly. > > I see quite often that users are asked for passwords because eclipse
> > does not pick the expected ssh keys. And if eclipse uses wrong ssh keys and
> > fails to authenticate to the host it falls back to standard authentication
> > which is by password.
>
> That may have happened for me at some point, because I was confused by the
> filled in username.
What I mean is that it may have happened that I entered the password for the username shown in the dialog for the corresponding host I wanted to connect to. But it was just asking for the passphrase of my private SSH key. Showing any username when prompted for the SSH private key passphrase was confusing enough for me to not read the message text properly.
Recommendation:
If egit is going to use SSH public key authentication and the configured private SSH key does require a passphrase in order to unlock it, *don't* show any username and just ask for a passphrase.
Thanks!
I understand what you mean. I fear we have no control over that dialog inside EGit. When Eclipse plugins want to do SSH transports they can make use of the jsch library (at least EGit does so). This library is in control to display any windows. But I personally don't see any problems with this username display: when you want to do transports with the URL 'ssh://myName@host.xy.z/path' and there is a password-secured ssh key available then the password dialog will list 'myName' (that name which you explicitly specified in the URL). I'll close this bug now because we can't do much about it. |