SSH Keys and Github

How to generate and set up a SSH key pair with Github.

To communicate with Github from our computers/servers we need to authenticate this communication with SSH key pairs. The way SSH keys work is you generate a key pair that consists of a private key and a public key. Each key contains a long line of encrypted text. The private key will exist on the computer/server you’re connecting from and the public key will be installed on Github via your Github account settings. When you attempt a connection to Github, the two keys are checked against one another and if they match up, the connection is authenticated.

NOTES

CHAPTERS
00:00 Introduction
01:50 Generating SSH key pairs
04:43 Installing public key on Github
06:44 SSH config for custom key name
08:28 Test it...

RELATED VIDEOS

PRODUCTS I USE
(paid links)

[azuboof]

Lovely. Thank you ms. susan simple concise and helpful

[benitajonah]

You have no idea how grateful I am for this omg. Thank you😭. I’ve spent days trying to get over this and it finally worked! Thank you so much.

[nagarajubattula]

Thank you so much for such a clear and thorough tutorial! So appreciated!

[dionnecf]

This video is brilliant. So clear and straight to the point. Saved me a lot of wasted time. Thank you

[camsmith]

Thanks you - really helpful easy to follow tutorial, especially supplying notes to accompany the video.

[nicolaecomaniciu]

Excellent video. All the documentation was narrowed down here perfectly

[TheTomorrowDream]

Perfectly explained, thank you so much !

[vasudevanbelakavadi]

Superb Simple Explanation - To The Point !

[SayedAli-vidz]

Thank you so much Susan, this helped me a lot !!

[dreamArmy]

Thank you so much !! Your video was really concise and clear.

[sydvic]

this video saved me a lot of time and headache

[sachinshrestha]

This video so much helpful . Thank you

[richard_loosemore]

The authenticity of host 'github.com (140.82.114.4)' can't be established.
ED25519 key fingerprint is
This key is not known by any other names.
Are you sure you want to continue connecting (yes/no/[fingerprint])?
The solution is quite simple. According to GitHub Docs, "Testing your SSH connection", you should look at the fingerprint it gives in the message and compare it with the official fingerprint at GitHub (see link on that doc page), and if the two match, you can go ahead and reply "yes" to the question and everything will be fine from that point on.
Of course, you could just reply "yes" without checking that they match, but that would leave you open to a classic man-in-the-middle attack, which would be awfully embarrassing. 🙂.

[Pavelbrov]

Thank you for the great tutorial and eloquent speech! I have a question: at 7:50, you added a key to the config file, but since there are many other files, how does SSH determine which one to use in each case?

[scarlettgriffith]

Thanks for video. I want to create SSH key, but I want other users also can use ssh to run git clone. what should I do?

[Uri]

I did all steps in ubuntu 22.04 aws instance, I'm succesfully authenticated... but when I try to clone.... ... fatal: could not create work tree dir 'my-repo': Permission denied