So humbled to read your message Sveta

So happy to know it

true this one helped me a lot

Most welcome!

Most welcome Arun

Glad it helped Scott

JP Let's delve into the intricacies of SSH key-based authentication. It's great that you're exploring this topic, and I'll clarify the processes for you. 1. SSH Key Pair Generation: - Client: The client generates an SSH key pair consisting of a public key and a private key. - Public Key: The public key is shared with the server. - Private Key: The private key remains securely on the client machine. 2. Server Configuration: - The server stores the client's public key in a special file (usually `~/.ssh/authorized_keys`). - The server marks the public key as approved for authentication. 3. Authentication Process: - When the client connects to the server: - The server sends a random string to the client. - The client encrypts this random string using its private key. - The client sends the encrypted string back to the server. - The server decrypts the received string using the public key. - If successful, the server authenticates the client. Now, let's address the difference you noticed: - Your Description: - The client decrypts the random string using its private key. - The client then sends back information to the server. - The server authenticates based on this information. - Video Description (as per your observation): - The client encrypts the random string using its private key. - The server decrypts the received string using the client's public key. - If successful, the server authenticates the client. Both processes are viable and achieve the same goal: secure authentication using SSH keys. The video's approach emphasizes the client's role in encrypting the message, while your description highlights the client's role in decrypting it. These are two sides of the same cryptographic coin In summary, both methods are correct, and they don't have different names. The key pair ensures secure communication, and the specific steps may vary slightly in how they're described Keep exploring, and feel free to ask more questions as you learn..

Excellent Hari

Most welcome Rachit

Most welcome Sundar

Glad it was helpful Jaikishan

You are most welcome

You're welcome!

Humbled to know this Nandhini

So nice of you

Thanks for watching Sandeep

Glad it helped Dayanand

Sure Radhika, I will plan a session

Thanks and welcome Neha

Most welcome

Most welcome Madhavan

Most welcome Santosh

I will do

Glad it was helpful!

Most welcome

I will plan for that Ram

@@RaghavPal thanks Raghav

You are most welcome Ayush

Glad it was helpful Ragesh

Most welcome Saifuddin

Thanks, will do!

Sure Ravi, Keep learning

Glad it was helpful!

Glad it was helpful

Thanks a lot

Most welcome Lucky

Most welcome Saurabh

Glad it was helpful!

You're welcome John

Always welcome

Most welcome Nachiket

Thank you 🙂

Most welcome Elavenil

Most welcome

Will be coming next week Dinesh

Thanks a ton Ganesh

Thanks Sophiya

Most welcome Biswa

You are very welcome Jimmel

You are most welcome Pooja

Sure, I will do

Most welcome Srikanth

You are welcome

Thanks Rajeesh

Most welcome Ahmed

Most welcome Yogesh

Glad it was helpful!

You are most welcome Kamalesh

Thanks for watching Odunayo

Will check on this Suhasini

@@RaghavPal thank you raghav

Most welcome 😊

I will do Peddi

Not yet, will need to check online

@@RaghavPal Thanks Raghav

Most welcome Eugene

You are most welcome

Glad it was helpful Kedar

Thanks for watching Tulasi

Hi Ebrahim, the person needs to have the authentic private key. Also it is recommended to secure your private key with password, so just in case someone gets access to you private key, he will still need to provide password to use it.

@@RaghavPal Got it! Many thanks for your reply 💜

You are welcome Tanveer

Most welcome Arun

Thanks and welcome Manish

Thanks for watching

Glad it was helpful Chaitanya

Thanks for watching Karteesh

Hi Sarthak Both these mechanisms are performed during the initial setup phase of an SSH session, and are not repeated in every message exchange. However, they are in place throughout the duration of the SSH session to ensure message integrity and prevent packet loss due to interleaving.

Hi Arun, will check on this

@@RaghavPal hi sir did you got any information?

Thanks, will do Abdul

Thanks Vamsi

default is port 22, but this can change

Thanks Sai

Hi Abhay, pls check this too - automationstepbystep.com/2020/07/23/a-story-of-ssh-secure-shell/

@@RaghavPal Thank you sir, do we have more link that shows actually how authentication takes place.

will need to search more online

you need to make a correction. encryption happens using the public key and decryption happens using the private key

Thanks Dhevan

Thanks

Thanks Toshit

Thanks and welcome Devendra

Hi Singaravelan, there is cryptographic fingerprint that is used to uniquely identify the keys.

thanks Tarun

Hi Manoj, I will need to check details

Most welcome Poorna

Hi Czar, yes so without encryption it will be a step easier for hackers, I am going a plan a security testing Q&A soon. that will help

@@RaghavPal thanks man

I will try to add a detailed session Aditi

Most welcome Nikhil

Hi Priya, will need to check your setup

@@RaghavPal Please suggest a way to check setup??

Yes, pls check here - automationstepbystep.com/

Thanks for the visit

I will do Faisal

Hi, I have not used ZOC, Can find more here - en.wikipedia.org/wiki/Comparison_of_SSH_clients www.slant.co/versus/499/5495/~putty_vs_zoc-terminal

sure

Thanks for watching Prakash