Updating SSH host keys - SourceTree

[Michelle McGinnis]

I am pretty clueless when it comes to SSH and keys. I've been using SourceTree/Bitbucket for a while now and have bunch of repositories set up & configured, connecting via SSH. Per this article that came out yesterday (https://bitbucket.org/blog/ssh-host-key-changes) there's going to be a change to the Bitbucket host keys. 

My local ssh key is RSA. I can't figure out where or what the Bitbucket host keys are. Do I need to do anything? 

[Yana]

Hi @Michelle McGinnis 

For SourceTree specifically, we have also added instructions to our public FAQ, depending on the version you are using MacOS or WIN.

Here is the link to the FAQ on how to update your known_hosts file for SourceTree: 

https://confluence.atlassian.com/bbkb/bitbucket-cloud-ssh-host-key-rotation-faq-1235851234.html 

We hope that after going through the steps and adding new Keys as outlined in the Blog https://bitbucket.org/blog/ssh-host-key-changes

you are able to switch to the newly introduced ECDSA or Ed25519 keys now. 

Let us know if you need further help. 

[Kimberly Luttenbacher]

Yes, scroll down on that article; just past the announcement are the instructions on what you need to do.  It's fairly simple and they also show you how to check.

If you want to see if it's already done without using their method, you can go to your .ssh/known_hosts file and see if the key is in there already.

example

vim ~/.ssh/known_hosts

I'm looking for this entry:

bitbucket.org ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDQeJzhupRu0u0cdegZIa8e86EG2qOCsIsD1Xw0xSeiPDlCr7kq97NLmMbpKTX6Esc30NuoqEEHCuc7yWtwp8dI76EEEB1VqY9QJq6vk+aySyboD5QF61I/1WeTwu+deCbgKMGbUijeXhtfbxSxm6JwGrXrhBdofTsbKRUsrN1WoNgUa8uqN1Vx6WAJw1JHPhglEGGHea6QICwJOAr/6mrui/oB7pkaWKHj3z7d1IC4KWLtY47elvjbaTlkN04Kc/5LFEirorGYVbt15kAUlqGM65pk6ZBxtaO3+30LVlORZkxOh+LKL/BvbZ/iRNhItLqNyieoQj/uh/7Iv4uyH/cV/0b4WDSd3DptigWq84lJubb9t/DnZlrJazxyDCulTmKdOR7vs9gMTo+uoIrPSb8ScTtvw65+odKAlBj59dhnVp9zd7QUojOpXlL62Aw56U4oO+FALuevvMjiWeavKhJqlR7i5n9srYcrNV7ttmDw7kf/97P5zauIhxcjX+xHv4M=
 

Since that was the last thing I did it's right at the end (in vim, you can go to the end with SHIFT+G, and you can exit the file with ESC :q)