Re: Multiple Keys in ssh-agent, fail to clone
> On Jul 13, 2016, at 3:32 PM, Junio C Hamano wrote: > > Benjamin Fritsch writes: > >> I read the Changelog for 2.9 and couldn’t find any reference to changed key >> handling. Is there anything that I can add to the `git clone` command to get >> the old behavior? > > I do not think this has much to do with the version of Git, unless > you are getting an updated SSH client together with your new version > of Git from whoever distributes it. Thank you for the great feedback. I could confirm that this is a problem on Bitbucket’s end. Sorry for the confusion. I managed to successfully clone with Git 2.9 and Git 2.8 Best, ben-- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Multiple Keys in ssh-agent, fail to clone
Hey all, We recently upgraded from Git 2.8 to 2.9 and saw an issue when there are multiple keys added to my ssh-agent. I have two keys. - KeyA (my company that has access to the repository I want to clone) - KeyB (just my personal key with access to my personal stuff) Having both keys in loaded and listed in `ssh-add -L` fails to clone the repository. I tried to change the order of the key in the agent but neither KeyA, KeyB nor KeyB, KeyA will work. The only case that works if I have KeyA loaded an no other key is added to the ssh-agent. Having multiple Keys loaded works with Git 2.8 and Git 2.7 (I didn’t try older versions) Cloning fails with “Unauthorized Access” of our Git provider. (It’s Bitbucket in this case) I read the Changelog for 2.9 and couldn’t find any reference to changed key handling. Is there anything that I can add to the `git clone` command to get the old behavior? Thank you for your help, Best Ben-- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
