Community
Participate
Working Groups
Build Identifier: 0.12.0.20110406 I can't connect to a assembla repository. (http://www.assembla.com) When I try to, Import > projects from git > clone, the dialog doesn't allow me to use the url needed for assembla: 'git@git.assembla.com:xyz.git' which is accepted by the commandline git clone statement. The suggestion from assembla to use git+ssh://git@git.assembla.com/xyz.git also fails as I can't change the user name needed to login as the dialog insist on setting the username to 'git'. When I try to create a project from existing git sources it fails on connecting to assembla as the "give passphfrase" dialog again provides the wrong username "git", which can't be changed. Reproducible: Always Steps to Reproduce: 1.Setup a assemble git repository 2.try to import/setup a project. 3.Fails to add working url+username+password
I created a test repo at assembla and tried pushing through ssh://git@git.assembla.com/test-assembla-11.git and this works for me (using current nightly build), could you give that a try ?
The problem is that to be able to push to an assembla git repo egit asks for my ssh rsa passphrase but it insists on using the username 'git' which it gets, I guess, from the assembla git url. The problem is that egit don't allow to change the user name. The whole problem is fixed, IMHO, if egit would allow the username to be changed. Presenting the user with a username seems a nice idea but it backfires in this case :-( Regards, Stas Zytkiewicz
I've cloned the assembla repo, a 'private' repo not the public test repo matthias has setup which will work of course as it doesn't require a ssh paraphrase. Then created a new project and added egit support by using 'right click on project' -> Team -> Share -> Git Now the project has egit support but as soon as I try to connect with the private assembla repo I get an internal error: " An internal error occurred during: "Pulling branch develop - braintrainer". ssh://git@git.assembla.com:22: Passphrase for /home/stas/.ssh/id_rsa " Regards, Stas
(In reply to comment #3) > I've cloned the assembla repo, a 'private' repo not the public test repo > matthias has setup which will work of course as it doesn't require a ssh > paraphrase. I don't see why decision to protect private ssh key with a passphrase is related to the privateness of the upstream repository. > Then created a new project and added egit support by using 'right click on > project' -> Team -> Share -> Git > Now the project has egit support but as soon as I try to connect with the > private assembla repo I get an internal error: could you provide steps what you did to "connect with the private assembla repo" ? > " > An internal error occurred during: "Pulling branch develop - braintrainer". > ssh://git@git.assembla.com:22: Passphrase for /home/stas/.ssh/id_rsa > " This looks like a bug, instead EGit should have shown a dialog to type in the passphrase. As we fixed quite some bugs since 0.12: could you retry with EGit 1.1 or a recent nightly build ?
(In reply to comment #4) > (In reply to comment #3) > > I've cloned the assembla repo, a 'private' repo not the public test repo > > matthias has setup which will work of course as it doesn't require a ssh > > paraphrase. > > I don't see why decision to protect private ssh key with a passphrase is > related > to the privateness of the upstream repository. Nothing, it's a private repo but Assembla uses ssh keys to determine ones permissions and my ssh key is protected by a passphrase. > > Then created a new project and added egit support by using 'right click on > > project' -> Team -> Share -> Git > > Now the project has egit support but as soon as I try to connect with the > > private assembla repo I get an internal error: > > could you provide steps what you did to "connect with the private assembla > repo" ? See my first mail. > > " > > An internal error occurred during: "Pulling branch develop - braintrainer". > > ssh://git@git.assembla.com:22: Passphrase for /home/stas/.ssh/id_rsa > > " > > This looks like a bug, instead EGit should have shown a dialog to type in the > passphrase. > As we fixed quite some bugs since 0.12: could you retry with EGit 1.1 or a > recent nightly build ? I have and now egit asks for a passphrase but ofcourse that would fail as egit tries to push with username "git" and my passphrase. The whole problem is that egit wants to be clever and tries to determine the git user name from the git url used by the assembla git repo. From the url 'git@git.assembla.com:xyz.git' egit insist that the username must be 'git' and this, wrong, username can't be changed in any of the egit dialogs. That's the whole problem. Make the username editable and there's no problem. And yes I can change the username in one of the conf dialogs but then egit starts to change the git repo url ??!! It will work if egit just drops it's "cleverness" and just uses the provided repo url and username, prompt for the passphrase, done. That's all.
I don't understand why EGit should ignore the user info if you provide it in the SSH URI and why you can't pass your username in the URL. Or do I misunderstand [1] ? [1] http://tools.ietf.org/html/draft-ietf-secsh-scp-sftp-ssh-uri-04#section-3.3
Does the problem still exist?
