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.

HTTPS SSH
  • 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>@bitbucket.org/<accountname>/<reponame>.git
SSH

git@bitbucket.org:<repo_owner>/<reponame>.git

もしくは

ssh://git@bitbucket.org/<repo_owner>/<reponame>.git

Mercurial HTTPS https://<accountname>@bitbucket.org/<repo_owner>/<reponame>
SSH ssh://hg@bitbucket.org/<repo_owner>/<reponame>/

Bitbucket supports two key encryption algorithms: RSA (R. Rivest, A. Shamir, L. Adleman) and DSA (digital signature algorithm)Create keys using the encryption method that is available to you.

Last modified on Aug 14, 2017

この翻訳に満足しましたか?

はい
いいえ
この記事についてのフィードバックを送信する

Not finding the help you need?

コミュニティへの質問

Powered by Confluence and Scroll Viewport.