{"id":2017,"date":"2013-09-18T18:02:42","date_gmt":"2013-09-18T18:02:42","guid":{"rendered":"https:\/\/www.anagram.at\/en\/get-gitbash-and-tortoisegit-up-and-running\/"},"modified":"2013-09-18T18:02:42","modified_gmt":"2013-09-18T18:02:42","slug":"get-gitbash-and-tortoisegit-up-and-running","status":"publish","type":"post","link":"https:\/\/www.anagram.at\/en\/get-gitbash-and-tortoisegit-up-and-running\/","title":{"rendered":"#gitbash, #tortoisegit"},"content":{"rendered":"
\n
\n

Set up SSH for Git<\/a><\/h1>\n<\/div>\n<\/div>\n
\n
<\/div>\n
\n

Up until this point, you have been using the secure hypertext transfer protocol (HTTPS) to communicate between your local system and Bitbucket. When you use HTTPS, you need to authenticate (supply a username and password) each time you take an action that communicates with the Bitbucket server. You can specify the username in the DVCS configuration file; you don’t want to store your password there though where anyone can see it. So, this means you must manually type a password when you use HTTPS with\u00a0 your local repository. Who wants to do that? This page shows you how to use secure shell (SSH) to communicate with the Bitbucket server and avoid having to manually type a password.<\/p>\n

Finally, setting up an SSH identity can be prone to error. Allow yourself some time, perhaps as much as an hour depending on your experience, to complete this page. If you run into issues, check out\u00a0Troubleshoot SSH Issues<\/a>\u00a0for extra information that may help you along. You can even skip this whole page and continue to use HTTPS if you want.<\/p>\n

\n
Linux or Mac User?<\/b><\/div>\n
\n

This page shows you how to set up and use a\u00a0single default SSH identity<\/em>\u00a0on Windows for a Git repository using GitBash. In the next page, you set up SSH for a Mercurial repository on Windows with TortoiseHg. If you are working on Mac OSX or Linux, a single set of instructions shows you\u00a0how to setup and identity for either Git or Mercurial<\/a>\u00a0in these environments.<\/p>\n<\/div>\n<\/div>\n

Step 1. Read a quick overview of SSH concepts<\/h2>\n

To use SSH with Bitbucket, you create an SSH identity. An identity consists of a private and a public key which together are a key pair. The private key resides on your local computer and the public you upload to your Bitbucket account. Once you upload a public key to your account, you can use SSH to connect with repositories you own and repositories owned by others, provided those other owners give your account permissions. By setting up SSH between your local system and the Bitbucket server, your system uses the key pair to automate authentication; you won’t need to enter your password each time you interact with your Bitbucket repository.<\/p>\n

There are a few important concepts you need when working with SSH identities and Bitbucket<\/p>\n