Check that both of your personal and work account have the correct public keys added for access. Github unable to get SSH keys working between sourcetree and github generating a new key with the putty key generator (SSH-2 RSA) entering a passphrase.Save the private and public keys for later use. Fresh Start: If you want to start from scratch, generate two new keys in PuttyGen.rsa to the file name so you can differentiate from your ppk format private key. Existing Keys: If you previously used Putty, load your ppk into PuttyGen and convert it to Open SSH format using the conversion option. I think that https makes it easier for people to get started since you dont have to do the whole generate/copy/paste ssh key business. ![]() We'll be implementing the scenario where you have 1 work and 1 personal Github/Bitbucket/Gitlab account Obviously this is Windows and Git specific. To generate an SSH Key, select Tools > Create or Import SSH Keys. Test your connection: type in the bash terminal ssh. Location: /Users/yyy/.ssh/idrsa where yyy is my user account name. I have recorded the steps I took to guarantee a sure-fire process to achieve functional Windows Sourcetree with Git working on multiple SSH keys. go to your GitHub account settings > SSH keys section and then click the New SSH key button. ssh-keygen -t rsa -C xxx where xxx is my e-mail address as a comment. What I found most interesting was that every document explaining how to do this omitted one or two critical details. Instead, you should use ssh -i /path/to/privatekey -T (you can leave you the -i /path/to/privatekey if youre using ssh-agent) Upon successful authentication, you should get a message like this: Hi. This week we have officially adopted two-factor authentication for our revision control so guess what?!Īs the documentation clearly states, this breaks HTTPS login for Git!Īll things considered this is a small issue but getting multi-key SSH configured was surprisingly difficult. If you try to connect with your GitHub username, it will fail: ssh -T > Permission denied (publickey). They continue to work with some repositories on Github but most attempts to push or pull result in an ssh rejection. ![]() To avoid SSH key issues we just use simple HTTPS to clone our repos down instead of hassling with multiple SSH keys. I have been using sourcetree for some time now and have had few issues. Sometimes we work from our personal computers and being developers, we have our own projects outside of work that are associated with different credentials. We use Git and Sourcetree, primarily on the Windows operating system and love it 99% of the time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |