SSH keys

If you don't have SSH configured, then you've been using the secure hypertext transfer protocol (HTTPS) to communicate between your local system and Bitbucket Cloud. Set up SSH to reduce the risk of exposing your username and password.

This table compares HTTPS and SSH to give you a better idea of the difference between the two.

  • Is suitable if you push to and pull from Bitbucket infrequently.
  • Requires you to enter a password each time you connect.
  • Is more effective if you push and pull from Bitbucket many times a day.
  • Removes the need to enter a password each time you connect.

The URL you use to access a repository depends on the connection protocol (HTTPS or SSH) and the distributed version control system (Git or Mercurial). You can find your repository-specific URLs from the repository Overview page. The following table shows these URL formats:

Git HTTPS https://<repo_owner><accountname>/<reponame>.git



Mercurial HTTPS https://<accountname><repo_owner>/<reponame>
SSH ssh://<repo_owner>/<reponame>/

Bitbucket supports four encryption algorithms for user keys: Ed25519, ECDSA, RSA, and DSACreate keys using the encryption method that is available to you.

Last modified on Dec 6, 2017

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.