Today I just had to spend the afternoon learning this technology properly for the first time in my career. I've always been a (L)user of SSH without really understanding how to use it properly, and this helped fill in the blanks. Thanks.
THIS! This tutorial is the only one of the 4 that I looked at that talked about the 'config' file in the user's .ssh directory. Quite frankly a game changer. I am certain that there are security tradeoffs somewhere with this file but based on the person's system permissions for the directory (users are advised to use chown to their own user and group) and the chmod to 700 so it's reachable, its just enough info to make ssh-ing sessions a lot less arcane and context switch intensive looking for secure passwords or whatever. Using a modern ssh key format like ed25519 makes complete sense as well from a security and speed perspective. What a great tutorial! So glad you posted this.
Not only gifted with Linux but also in teaching and explaining. Really appreciate it. I had several domestic servers. Just moved to linofe and paid for my first server.
18:11 When closing the terminal, the ssh-agent does not close. You can simply export the two environment variables (SSH_AUTH_SOCK and SSH_AGENT_PID) from the previous terminal and everything will work the same way.
@@rexby i figured it out using keychain instead of dealing with ssh-agent directly. But I meant I didn't know how to export the environment variables like you mentioned.
As an old retired tech admin guy, this brings back a lot of good memories. You showed some good advanced techniques to keeping everything secure while easy to manage. Good job!
Acme is from Looney Tunes where Coyote order everything, Shinra is from Final Fantasy VII is the Malevolent Corporation and Skynet is from The Terminator the evil computer system from the future.
Thank you for such a useful guide! I have another issue, I have 3 PCs (home, work, laptop) and I need to have access to my server from all my workplaces. Is it better to duplicate them or should I generate new ones for all PCs?
I've seen a lot of your content, very well done. I have a question on this topic, is there a way on Windows to setup my .ssh keys as you've demonstrated on your Linux client?
ACME - Classic cartoon company that Wile E. Coyote would get all his good from to capture Road Runner Shinra - I had too Google. Either Fire Force or Final Fantasy 7 Skynet - AI from Terminator
Is it really necessary to run ssh-agent after adding keys to config file? Because I always assumed that the SSH command would read its parameters from the config file Hence no need for ssh-agent.
no. it's a specific cryptographic standard. "Ed" from Edwards (twisted elliptic curves) "25519" from Curve25519, which is a specific mathematical description of one of the components used.
Hearing "shinra" out of nowhere really soothed the pain of having to learn how to juggle multiple different identities with no GUI and very little understanding of Anything Involved; thank u. This would be an amazing tutorial either way but now I'm thinking about how pretty they made Cloud in the ff7 remake instead of how mad GitHub makes me
I have created 2 ssh keys, but there is something that i don't understand. I cannot associate my ssh keys, i'm using a personal github account, and another gitllab account, i want to use both ssh keys to work with diferent repositories. But when i try to associate a key with "the server" as $ ssh -i ~/.ssh/githubexample_key githubexample always appears this error => ssh: Could not resolve hostname githubexample The thing is that i don't know "how to get to the gitlab server", or "the github server", by the other hand i understood (maybe missunderstood) that the server is connected with the name of the key before the underscore.
Today I just had to spend the afternoon learning this technology properly for the first time in my career. I've always been a (L)user of SSH without really understanding how to use it properly, and this helped fill in the blanks. Thanks.
THIS! This tutorial is the only one of the 4 that I looked at that talked about the 'config' file in the user's .ssh directory. Quite frankly a game changer. I am certain that there are security tradeoffs somewhere with this file but based on the person's system permissions for the directory (users are advised to use chown to their own user and group) and the chmod to 700 so it's reachable, its just enough info to make ssh-ing sessions a lot less arcane and context switch intensive looking for secure passwords or whatever. Using a modern ssh key format like ed25519 makes complete sense as well from a security and speed perspective. What a great tutorial! So glad you posted this.
Just so happy I found this.
My headache is solved.
Thanks.
Went through a quite a bit of tutorial flops before I found this gem. Thank you!
Not only gifted with Linux but also in teaching and explaining.
Really appreciate it. I had several domestic servers. Just moved to linofe and paid for my first server.
18:11 When closing the terminal, the ssh-agent does not close. You can simply export the two environment variables (SSH_AUTH_SOCK and SSH_AGENT_PID) from the previous terminal and everything will work the same way.
Hey you dropped this 👑
@@AceptronThank you
I'm still pretty new to the terminal, can you explain a little better what you mean please?
@@jhonyortiz5 What exactly do you not understand?
@@rexby i figured it out using keychain instead of dealing with ssh-agent directly.
But I meant I didn't know how to export the environment variables like you mentioned.
Literally needed to do this today and found this immensely helpful
This is super useful - thanks. Love that you explain things STEP BY STEP with increasing sophistication
As a content creator I must say, your video's are well done, easy to follow, and very useful!
Explained flawlessly, thank you for this video
Thank you a lot for this video! I spent a couple hours trying to figure it out why my others ssh keys were not working.
This is explains things very well. I have been overwriting my ssh keys! My dog thanks you! He will get less kicks in the future...
Very useful, thanks!
You are the Gigachat of linux explanations.
Thanks a lot! Very helpful.
Amazing. Thank you so much!
awesome 💪 didn't know about the ed25519 key type
wished it was called ed209
Thank you!
thanks a lot very helpful !!!
As an old retired tech admin guy, this brings back a lot of good memories. You showed some good advanced techniques to keeping everything secure while easy to manage. Good job!
thanks for very usefull lesson
Thanks and God bless.
Acme is from Looney Tunes where Coyote order everything, Shinra is from Final Fantasy VII is the Malevolent Corporation and Skynet is from The Terminator the evil computer system from the future.
Thank you for such a useful guide!
I have another issue, I have 3 PCs (home, work, laptop) and I need to have access to my server from all my workplaces.
Is it better to duplicate them or should I generate new ones for all PCs?
I've seen a lot of your content, very well done.
I have a question on this topic, is there a way on Windows to setup my .ssh keys as you've demonstrated on your Linux client?
Hi, do you create a separate key for every server or for every user on a server as well? thanks
Great video !!!
Thanks for sharing
Wow, very good explanation!
How can combine ssh key with two factor?
Can I use together?
Liking for the FFVII reference!
ACME - Classic cartoon company that Wile E. Coyote would get all his good from to capture Road Runner
Shinra - I had too Google. Either Fire Force or Final Fantasy 7
Skynet - AI from Terminator
Is it really necessary to run ssh-agent after adding keys to config file? Because I always assumed that the SSH command would read its parameters from the config file Hence no need for ssh-agent.
What about Umbrella Corp...?
why its ed25519 ? are these numbers that you just want at your choice?
no. it's a specific cryptographic standard.
"Ed" from Edwards (twisted elliptic curves)
"25519" from Curve25519, which is a specific mathematical description of one of the components used.
Skynet is from 'Terminator'.
ssh-copy-id is great and all, but still leaves password authentication enabled.
Why use *CTRL-O* ? Just enter: *CTRL-X Y* in "nano"
Or just hold down Ctrl then do S, X
topclass
Hearing "shinra" out of nowhere really soothed the pain of having to learn how to juggle multiple different identities with no GUI and very little understanding of Anything Involved; thank u. This would be an amazing tutorial either way but now I'm thinking about how pretty they made Cloud in the ff7 remake instead of how mad GitHub makes me
how do you upload the key to the server if password authentication is turned off?
Account creat nhi ho raha hai
Mooji
I have created 2 ssh keys, but there is something that i don't understand. I cannot associate my ssh keys, i'm using a personal github account, and another gitllab account, i want to use both ssh keys to work with diferent repositories. But when i try to associate a key with "the server" as $ ssh -i ~/.ssh/githubexample_key githubexample
always appears this error => ssh: Could not resolve hostname githubexample
The thing is that i don't know "how to get to the gitlab server", or "the github server", by the other hand i understood (maybe missunderstood) that the server is connected with the name of the key before the underscore.