| Summary: | Egit won't ask for passphrase and fail with "Cannot list branches. Reason: … Passphrase for | ||
|---|---|---|---|
| Product: | [Technology] EGit | Reporter: | Christian Campo <christian.campo> |
| Component: | UI | Assignee: | Project Inbox <egit.ui-inbox> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | konrad_w, nightych |
| Version: | 1.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Christian Campo
It seems that Egit asks actually for the passphrase when I do Team -> synchronize workspace. Just the clone command wouldn't…. (if that makes any sense) Same problem here, if I'm trying to push (Win 7, Indigo, EGit 1.1.0). It displays an error message instead of the password dialog box. The text of the error is exactly the same as if the dialog would appear, therefore I guess EGit mistakes the response from the server as an error. Workaround: Open Git Repository Exploring View, select your repository, rightclick on Remote -> Create Remote. When you create your remote repository, it will show the passphrase dialog as expected. Please retry with a current nightly build version. I just tried (version from 2011-11-25) and it works as expected. This is still a problem with eGit 3.0.3 in Kepler SR1. I am asked for a passphrase when issuing "Push" via Right-Click on the Remote within the Git Repositories View. It does not work though when Push is triggered from the Project Explorer View Team->Remote->Push... It just outputs the following error message in a modal dialog (which is not logged in the Error Log unfortunately): ssh://git@<some git URL>: org.eclipse.jgit.transport.CredentialItem$StringType:Passphrase for /Users/<username>/.ssh/id_rsa ssh://git@source.int.netcentric.biz:7999: org.eclipse.jgit.transport.CredentialItem$StringType:Passphrase for /Users/<username>/.ssh/id_rsa It works fine, once the passphrase was once entered, but in my regard the dialog asking for the passphrase should also be triggered from the Project Explorer View. |