Bug 330 - Git requires password authentication for push/fetch and does not use keys
Summary: Git requires password authentication for push/fetch and does not use keys
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Version Control ()
Version: 2.6 Beta 3
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Alan McGovern
Depends on:
Reported: 2011-08-19 01:18 UTC by Wolfgang Silbermayr
Modified: 2012-02-14 07:31 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Wolfgang Silbermayr 2011-08-19 01:18:53 UTC
When trying to push to or fetch from a server using Git over SSH, a password dialog is shown in any case. The SSH user does not have a password on the server, but is authenticated using the private-public-key method. This is used by default for platforms like Gitorious (and if I remember correctly, Github as well). When I am using the command-line on Linux, the push works perfectly without any interaction.
Comment 1 Alan McGovern 2012-01-06 12:27:45 UTC
Ngit has no integration with the MacOS keychain or ssh agent so this is why you are prompted again for your ssh passphrase. I just finished implementing initial support for storing usernames/passwords in the MacOS keychain and added support for storing passphrases there. Once this support is in monodevelop master you will be prompted to store the passphrase and thus will never need to enter it again. This will not happen until at least monodevelop 2.8.7 though.

Thanks for reporting this.
Comment 2 Alan McGovern 2012-01-06 12:28:36 UTC
Actually, can I double check that you actually have a passphrased ssh key. Is the dialog you are given prompting you for a passphrase or do you end up having to log in with a username and/or password?
Comment 3 James 2012-01-06 18:01:27 UTC
I use Ubuntu and my experience is that it will not prompt me for a passphrase for my private key at all. 

When I try to do a push with Monodevelop I always get a password box, but the password box that comes up will only accept the account password even if I have openssh configured to log in with my private key. 

I have not tried using a key without a passphrase.
Comment 4 Alan McGovern 2012-02-14 07:31:16 UTC
This should all work with MonoDevelop 2.8.6 and higher. If you experience any issues with these newer builds, either reopen this bug or file a new one. The next major release of monodevelop (due to happen in the next few weeks) should have even better support for the differing authentication methods.