I fixed this after I realized that I connected to a target host of the same name earlier and then rebuilt it so there was an old key in.sshknownhosts.

This will stop prompts to accept new host keys, but it will save each host key for future connections in knownhosts.

What the question wants is ssh to auto-accept and redirect to devnull.

Provide details and share your research But avoid Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

Chat with others in the program, or give feedback to Atlassian.

The Atlassian people really should have documented that this will probably happen in their instructions.

Whenever SSH tries to log in to a host it hasnt seen before, it will put up a message like this.

Do you really want to connect And in really secure environments, youd actually compare the fingerprint with the fingerprint that you had been given before to make sure youre not connecting with an imposter host.

But you really are trying to connect to bitbucket.org.

So you can go ahead and say yes and you should continue logging in.

Someone could be eavesdropping on you right now (man-in-the-middle attack).

It is also possible that the RSA host key has just been changed.

Add correct host key in.sshknownhosts to get rid of this message.

RSA host key for bitbucket.org has changed and you have requested strict checking.

CEDRIC ZABEL I have same issue, but when i say yes its answer me like: bitbucket.org: Permission denied (publickey).

I dont have any SSH in my repository (i tying made some, bat didnt use it and deleted).

Just trying clone my data from bitbucket to new location (new pc).

Host an event Youre one step closer to meeting fellow Atlassian users at your local event.

Host Key Fingerprint