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?
Good question! It will try each of them you have listed, stopping if it gets to one that works. To see the details of this, you can add the -v (verbose) flag to your SSH command (ssh -Tv git@github.com) and it will show you all the details of the connection attempt, including output on which keys it tries.
It seems it tries only the first key in the list and if the key is wrong, then the process fails. So we have to put the key at the top to make it work(
In the settings for a repository on Github there is a Collaborators section where you can give other Github users access to that repository. As long as they have a SSH key set up with Github for the account you give access to, they should be able to clone the repository.
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
You might get a weird message when you try to test the ssh key at GitHub (using ssh -T git@github.com): The authenticity of host 'github.com (140.82.114.4)' can't be established. 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])? 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. 🙂.
thanks for that brother, I got this after that "Hi USERNAME! You've successfully authenticated, but GitHub does not provide shell access." is there anything wrong with this?
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.
Awesome!! One of the best and easiest Terminal and GitHub video tutorials I've seen 🙏
This video is brilliant. So clear and straight to the point. Saved me a lot of wasted time. Thank you
Thanks you - really helpful easy to follow tutorial, especially supplying notes to accompany the video.
Excellent video. All the documentation was narrowed down here perfectly
Glad it was helpful.
Lovely. Thank you ms. susan simple concise and helpful
Thank you so much for such a clear and thorough tutorial! So appreciated!
Thanks for watching!
Perfectly explained, thank you so much !
Superb Simple Explanation - To The Point !
Thank you so much !! Your video was really concise and clear.
this video saved me a lot of time and headache
Thank you so much Susan, this helped me a lot !!
This video so much helpful . Thank you
Thank you so much you are a savior
Great work!
This is very useful.
Glad you found it helpful, Upendra.
@@codewithsusan Thank you so much for this video 👏
you saved my life
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?
Good question! It will try each of them you have listed, stopping if it gets to one that works. To see the details of this, you can add the -v (verbose) flag to your SSH command (ssh -Tv git@github.com) and it will show you all the details of the connection attempt, including output on which keys it tries.
It seems it tries only the first key in the list and if the key is wrong, then the process fails. So we have to put the key at the top to make it work(
Nice explanation
Thanks, very helpful!
awesome!
this is great
this is very helpful thanks
Thank you! Subscribed
awesome thank u for this 💙
Welcome 😊
Pedidos de vídeos futuros
Thank you so much!!
Thank you so much for such
Thank you so much !!
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?
In the settings for a repository on Github there is a Collaborators section where you can give other Github users access to that repository. As long as they have a SSH key set up with Github for the account you give access to, they should be able to clone the repository.
Nice
subscribed!
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
See my reply here: th-cam.com/video/c6ZsjOvGMGM/w-d-xo.html&lc=UgzMGTlafbxh1sgYayh4AaABAg.9tAAWEHKmRm9tCBkgMJQR9
thank you
”Subscribed!”
You might get a weird message when you try to test the ssh key at GitHub (using ssh -T git@github.com):
The authenticity of host 'github.com (140.82.114.4)' can't be established.
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])?
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. 🙂.
thanks for that brother, I got this after that
"Hi USERNAME! You've successfully authenticated, but GitHub does not provide shell access."
is there anything wrong with this?
nice!
Thanks
thanks
nice
great
darn it, it was a clear video but didn't work for me yet (I think it's thanks to me using Windows instead of Linux...)
gg
e
Thank you so much for such a clear and thorough tutorial! So appreciated!
Thank you so much !! Your video was really concise and clear.
subscribed!
Nice
gg