Trust A Server's Host Key when No Button is Available to Trust It
Problem
Users may not be able to trust a server's host key that is not cached in the registry via SourceTree's output when the user is using System Git. Example:
git -c diff.mnemonicprefix=false -c core.quotepath=false fetch origin
The server's host key is not cached in the registry. You
have no guarantee that the server is the computer you
think it is.
The server's rsa2 key fingerprint is:
ssh-rsa 2048 aa:d1:aa:00:bb:c0:b0:a0:d0:e0:f0:a0:a1:00:11:ee
If you trust this host, enter "y" to add the key to
PuTTY's cache and carry on connecting.
If you want to carry on connecting just once, without
adding the key to the cache, enter "n".
If you do not trust this host, press Return to abandon the
connection.There's no button provided to click enter yes or no, or any space to type in a "y" or an "n".
Workaround
There are two workarounds:
Option 1
Just get SourceTree to use Embedded Git and get it to trust the host:
And then change it back to System Git.
Option 2
Run the command below in your command prompt.
"C:\Program Files (x86)\Atlassian\SourceTree\tools\putty\plink.exe" bitbucket.orgIf you've changed the SourceTree installation directory, you would need to modify the command.
"C:\<Path>\Atlassian\SourceTree\tools\putty\plink.exe" bitbucket.org
You may follow the steps below:
- Press the _Start_ button
- Search and execute the _Command Prompt_
Run the command:
"C:\Program Files (x86)\Atlassian\SourceTree\tools\putty\plink.exe" bitbucket.org- Enter y to accept the server key
This should resolve the issue.
Last modified on Jun 21, 2016
Powered by Confluence and Scroll Viewport.