FIX: The authenticity of host github.com can't be established.

fix_authenticity_of_github_problem.md

Error

The authenticity of host 'github.com (140.82.113.4)' can't be established.

Fix

ssh-keyscan github.com >> ~/.ssh/known_hosts

Example (eg. using CircleCI workflow)

- run:
    name: Add github.com to known hosts
    command: ssh-keyscan github.com >> ~/.ssh/known_hosts

Thanks!

Thanks a lot

Testing your SSH connection

thanks for your comment, it was very helpful to me

thanks @tomigee

How can I check if it worked please? I got the below output after entering the command.

ssh-keyscan github.com >> ~/.ssh/known_hosts

github.com:22 SSH-2.0-babeld-dd067d10

github.com:22 SSH-2.0-babeld-dd067d10

github.com:22 SSH-2.0-babeld-dd067d10

github.com:22 SSH-2.0-babeld-dc5ec9be

github.com:22 SSH-2.0-babeld-dd067d10

what I'm I supposed to do to check if it worked?

open file known_hosts,then copy fingerprint to tortoisegit input box,then input yes, and you will be able to pull code

ED25519 key fingerprint is SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU. This key is not known by any other names Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added 'github.com' (ED25519) to the list of known hosts. git@github.com: Permission denied (publickey). Im getting the same issue Firstly I couldn't add rsa format ssh in the deploy keys, warning was thrown to add an openssh format after creating an ssh with ED25519 format github didn't threw an error but on my linux machine I'm getting this error

problem like me right now

User beware: doing this method above leaves you vulnerable to man-in-the-middle attacks. Instead, I'd recommend following GitHub's documentation on Testing your SSH connection. Pay special attention to the step where they ask you to compare the fingerprint returned in command line with GitHub's public fingerprint.

Follow this instructions it is the right process

It worked!!! Thanks 💙

that worked for me! thank you ❤️

User beware: doing this method above leaves you vulnerable to man-in-the-middle attacks. Instead, I'd recommend following GitHub's documentation on Testing your SSH connection. Pay special attention to the step where they ask you to compare the fingerprint returned in command line with GitHub's public fingerprint.

Read line by line, and you will get the light.
Thank you 👍

thank you it worked!