@palaniappanrm6277

The missing puzzle in all your existing CA/TLS video was what the CA exactly does which is explained here. It takes the public key of the server and signs (generates digital signature) with his private key so that any clients can decrypt the content and verify if the public keys are the same to trust the server. Love to learn more from you. Thanks 👍

@akankshyadas9759

the confusion i was having for the last few weeks just vanished away at 5:12 , nobody on this platform ever bothered to mention that this was an old method and the new method incorporates DH key exchange algo. THANK YOU A LOT HUSSEIN !

@dhruvkaith3160

I understood public key cryptography, but was looking for how these certificates are exchanged. This explanation was spot on, thank you so much.

@CANIHAZURDREAMSPLS

This guy's voice is perfect for teaching. So relaxing and calming :)

@len_kimjones8320

This is by far the best explanation I've seen on SSL certificates. Thank you!!

@melika09

This is the best explanation that I've seen about keys and certs. Tanx Man!

@aaronestes3282

"take my public key beautiful" lmfao

@preetiptl

Man, you are genius!! I’ve spent almost an hour checking other videos about ssl but couldn’t understand it completely. But the way you explain it, it’s super clear now. Thanks a lot

@baracudda21

Thanks!

@SalmanAli-me9ce

I've just watched this video ten times just to enjoy the stuff. Really cool way of teaching.

@davee.4847

This left no questions open, amazing.

@ahmedakef

really this is a great explanation
but at 11:45 you say that the way of  verification is that it encrypt the certificate with the certificate authority public key and check if it output the same signature, I think this is not a way of verification as if the signature is the encryption of the certificate using the public-key then any one can fake the certificate easily

I think the only of verification is the other way you mentioned in 11:54 which is decrypting the digital signature using the public-key of CA which result in a hash then compare this hash with the hash of the content of the certificate and if it match, then everything is correct 

I think that I read before that in digital signature, it is created by encrypting the content using private-key and other people decrypt it using the public-key

@richardwang3438

Here is my comment, son.
This is a great video, thanks

@mosup5007

I like your personality and your way of teaching. Listening to you is entertainment and learning at the same time. Keep up man ❤️

@NK-iw6rq

Thank you Hussein, I am an IT student and this video helped me so much !

@Sathish12121

Wow what a clear insight.when i search for this in youtube i got a video a guy in dark light and writing in transparent board but it was nothing near to your videos but his video got 100k views wondering comparing to that your content deserves 1M views. You’re missing some YouTube strategies

@dhruvshettty

I believe this channel is going to become the next Khan Academy for technology

@giri455161

Really helpful lecture to understand the fundamental of exchanging the keys and how do they encrypt.

@vaughnbay

This entire process reminds me of the mid to late 70's.  Every software developer out there was developing software by throwing software spitballs at the wall to see what would stick.  The  game was to capture market share by being first to market regardless of how good or bad the software was, and then go back to fix all the bugs after release.  The product did not matter,  you simply had to get sufficient market share to control the standards and hence the licensing.  It happened time after time.  50 years later and it's still going on.

@1337purpose

Amazing explanation Sir Hussein keep it up!!