
Questions about SSH workaround Is my SSH connection to Bitbucket Cloud still secure using this workaround? Follow this Community post or watch the BCLOUD ticket to be notified. Once we have provided that update, you may safely revert the changes you made per the instructions in this article.
#Openssh github update#
The Bitbucket team is working on adding the updated signature support to our SSH server and we will provide another update once these changes have been implemented, tested, and deployed to our production infrastructure. To remove this workaround in the future, follow the same instructions to change your remote URL back to the SSH URL. We recommend using an app password for automated git clients such as build machines or if you have two-factor authentication enabled. Switching to HTTPS will require using a different authentication mechanism. Therefore, you can avoid this issue by updating your git client to use HTTPS instead of SSH to talk to Bitbucket Cloud by following the instructions on this page. HTTPS connections to Bitbucket Cloud are unaffected by changes to the OpenSSH client. On Windows systems, this configuration is located at %USERPROFILE%\.ssh\config or %PROGRAMFILES%\Git\etc\ssh\ssh_config. On Unix-like systems, this configuration is located at $HOME/.ssh/config or /etc/ssh/ssh_config.

You can continue to use SSH by adding the lines below into the Host section of your SSH configuration: If you are receiving the warning above, there are two options: updating your SSH config locally, or switching from SSH to HTTPS. Since Bitbucket Cloud’s SSH server does not yet support the newer preferred algorithms ( rsa-sha2-256 and rsa-sha2-512), affected SSH clients are unable to complete authentication and an error is displayed.īitbucket Cloud engineers are actively in the process of adding support for these algorithms as a part of the SSH connection process.

Default configurations of some newer SSH clients have dropped support for older signature algorithms used during the authentication process.
