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. The private key resides on your local computer and the public you upload to your Bitbucket account. An identity consists of a private and a public key which together are a key pair. To use SSH with Bitbucket, you create an SSH identity.
SETUP SSH FOR BITBUCKET MERCURIAL WINDOWS HOW TO
If you are working on Mac OSX or Linux, a single set of instructions shows you how to setup and identity for either Git or Mercurial in these environments. In the next page, you set up SSH for a Mercurial repository on Windows with TortoiseHg. This page shows you how to set up and use a single default SSH identity on Windows for a Git repository using GitBash. You can even skip this whole page and continue to use HTTPS if you want. If you run into issues, check out Troubleshoot SSH Issues for extra information that may help you along. Allow yourself some time, perhaps as much as an hour depending on your experience, to complete this page. 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.įinally, setting up an SSH identity can be prone to error. So, this means you must manually type a password when you use HTTPS with your local repository.
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. 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. Up until this point, you have been using the secure hypertext transfer protocol (HTTPS) to communicate between your local system and Bitbucket.
0 kommentar(er)
