I love your teaching style. Do you have interest in sharing one of your already made courses with our channel?

By far this is the best video i have seen on CA. Everybody explain these concepts in a peripheral way and we will end up more confused. Here you have done a great job. Thank you!

Fantastic! I could never wrap my head around how you get a mutual key established over the Internet without someone being able to snoop it, and this finally made the connection for me. Plus certificates make more sense now.

This is BY FAR the most educational video I've ever seen on this topic. Thanks a lot! It made a huge difference that you really started at the bottom instead of building on knowledge of other (confusing) stuff.

Only video in the UKposts where you can come with pretty much zero or very basic knowledge of networking, internet security and still be able to understand SSL/TLS certificate better and very clearly than an average CS students know of..! Simply amazing teaching skills! 👌♥️

Rarely I comment on videos, usually, I stick to liking or disliking to provide feedback. However, I couldn't resist commenting on this video-such an incredible way to explain the intricacies behind how things work!

I've been searching for a detailed description of how the certificate chain of trust works. This is the best I've come across, by far! Thanks for posting!

Accidentally clicked on this video, but after nearly an hour of watching, what I got was satisfaction. You're doing a great job! Thanks!

After watching the video, I just could not help asking myself who is making this video. The quality, the details, the PowerPoint slides, the detailed explanation left me wanting more content in this manner. You have a skill. Another thing that I might add. One can say that your video is long (took me three seating to complete it) but the knowledge that I came out was unbelievable. I understood the topic 100 percent. Don’t see how you could have made it shorter. Amazing job. Can wait for new content and I am looking at other videos and topics that you have done as the content has to be amazing.

Great video! Last and most important thing that you didn’t notice in your video. Root CA Verification. The browser has a pre-installed list of trusted root CA certificates, which it uses to verify the authenticity of the root CA certificate presented by the website. The browser checks whether the root CA certificate presented by the website is signed by a root CA that the browser trusts.

It is great you went all levels in OSI model. Sometimes staying at the abstractions of higher layers can confuse or make learners assume wrong ideas! Great video

Thank you for making this video. This is exactly what I was looking for after wasting time watching 3 or 5 minutes videos on this topic. Now I understand it. Love your teaching style.

The video starts from basics that's what makes it easy to understand and relate. So far one of the best videos on this topic. Amazing stuff. Thank you for putting this together.

Bro, your lectures are way above college level. I mean, I learn here way more by watching your explanatory video than actually going to college. Thanks for taking the time to be as considerate enough in sharing all of this valuable info. I agree, also with some of the comments down here, you're easy to follow and man I've learned so much in that 43 minute explanation. You should create your own courses and sell them online just saying, given your potential. Anyhow, wishing all of the best.

As a cyber security student this video was very informative. It flowed very smoothly and didn't feel bored at all (even though it was 40mins). Very good video. thank you laith academy.

you are one of the best teachers out there i really appreciate you and your work.

The best explanation on the topic. Kudos for the remarkable effort you have put in! ❤

a very well explained tutorial.... was searching all internet for something like this and got stuck with your vedio and YOU NAILED IT ....... Thanks for such an explanatory video !!!

at 22:32 minutes I fully understand how secure communication happened at the first place !!! Awesome work as you do always Love from Pakistan

Great content! I thoroughly enjoyed your explanation; it was simple and easy to understand. Keep up the fantastic work!

The best explanation I have come across on this topic! 🙌

just watched your nginx course, you're really good at explaining man! definitely gonna watch more of your videos

instructor like u deserve better bro i have been watching you videos for long time they are so good even you are better than most famous youtuber. you know you are the best instructor also most underrated instructor you deserve better.

Crazy explanation ❤❤❤ in an hour I am attending client round I am 200% confident right now

This is the best explanation of Cryptography concept, Thank you so much for making this.

Best video on SSL certificate on any platform.. thank you so much!! You just earned a subscriber :)

Thanks a lot for making this video. Helped me understand clearly how the complex process of encryption works

Amazing video, thank you for such labor to make it for people who doesn't really know all this stuff

best video out there that explains all this. thank you for your efforts!

Thanks! You work for hello fresh, this is so cool! I'm revisiting this process, it has been a while since i saw it at college. This is more complicated than i remember, but basically the CA Authority is encrypting an already public server key not to protect against decryption, but it is doing for the purpose of signature, because only the CA Authority could have ever issued an encrypted 'thing' that can be decrypted with the CA Authority public key. And we can check that the 'thing' after the decryption is correct because it is attached to the certificate. This very cool and well explained, appreciate the video. And if you read this please correct me if my understand is wrong on this.

Thanks for detailed explanation ,Best ever explanation i have come across FOR SSL HTTP AND HTTPS❤

Man this video is very nice and need, a little bit extended, but needed

Thanks for your pedagogy, I really appreciated your video.

Amazing content! loved it, thanks for this.

God Bless you for this video.

great video, worth the time watching. but one thing to add to the video is that asymmetric encryption is used only during the "symmetric encryption public key' exchange period, after that, symmetric encryption will be used. the reason is symmetric encryption is far more efficient.

Absolutely great content, I learned a lot!

One of the best and detailed video video ,so amazing explanation ❤

Very good explanation. I am myself a programmer and didn’t really get a clear picture of https into my head. Thank you very much!

I certainly do appreciate this tutorial 💯, thank you very much! :-)

Superb video on https. Thanks for the elaborate, clear explanation.

Great Video.Thanks for your Time and Effort.It really helps.

Finally... I understood this concept thanks to you...

Very well explained.. Appreciate your good work. 👏👏

Thank you!!!! This was a great video and really well explained!

Thanks a lot Laith Academy... great stuff and very well explanation.

Fantastic as always. thanks for your useful tuts 💗

Thank you so much for detail explanation.

Nice video, but you could have also mentioned that the certificate is very tied to the website's domain name. You could also have said that the CA company checks the credibility of the certificate applicant and whether the domain name has been purchased by the applicant. And a technical detail - CA does not encrypt the applicant's public key with its private key. It only digitally signs the certificate. To digitally sign a document/file - we do not encrypt the entire file or its part with our private key. Because a 1GB file after encryption will give us a 1GB encrypted file. Therefore, we create a hash of this file, which is much smaller. Then we encrypt this hash with a private key and add the encrypted hash (digital signature) to the file. In this case, the document is the applicant's certificate. It should be mentioned that if at least one bit of the file/document changes, its hash will also change - this is how hashing algorithms work. So, it is impossible to replace the website's domain name in the certificate without changing the hash and, consequently, the digital signature. If something in the certificate changes, the CA must sign a new one again. And this is very important, because the browser first of all checks whether the website's domain name entered in the address field is identical to what is included in the certificate sent by that website. Because of that it is sure, that it enters the correct site. But the certificate could be fake. So, in second step it checks the certificate as well. Browser creates a hash from the certificate, uses the CA's public key to decrypt the hash/signature, and compares these hashes. If they are the same, the certificate is OK. This proves that the certificate has not been changed along the way and comes from the owner of the domain/website. And only when the domain name of the website is the same as in the certificate and the certificate is verified positively, only then does the browser trust the website it wants to visit - and a padlock appears. Greets.

Super nice, impressive slidedeck!

absolutely wonderful, thank you :)

Thank you! this is so well explained ☺

huge thanks! really useful explanation!

Hey buddy, this is a amazing video, really nicely described. I have subscribed right away and am looking forward to seeing more videos. I'm grateful.

Thank u so much this is really helpful and the best one so far

super, excellent, very good explanation. very good teacher

complimenti, chiarissimo. Grazie

Great details, thanks. 🙂

Great video ans love your presentationand teaching method, keep it up

Excellent info thanks Laith.

Great video! I learned a lot in one video.❤❤❤❤❤

luv ur explaination bruuu

Perfect .. Very well explained

love the explanation.

You are the Best !!!

This's almost perfect explaination

great explanation!

Excellent video

completed !!! to be honest never seen such a wonderful explanation on such complex topic Regard: Kim from Pakistan

Great Video

Excellent video 👌 The only thing that I feel is missing is the a slide showing/explaining how the usage of Certificate with conjunction of CA actually prevents the man-in-the-middle problem.

Great vid3o. Well explain

This is really good, answers to alot of questions (I didn't even know how to ask 😂)

Wonderful explanation

Thank you!

perfect explanation..

great video thanks for it ❤❤

Thank You!

Great explanation thx

bravo much appreciated

Very good video!

great Video

Very helpful video :)

Very informative

Its awsome !!!!!!!

For your MERN subscription project, how do you deploy the app from localhost 3000 and localhost 8080 to the actual web app domain?

@Laith Academy: Thanks for the detailed explanation. I have a doubt at 32:55 timestamp The Facebook user browser doesn’t decrypt, instead performs signature verification with CA’s public key.. is my understanding correct? Because public keys used for encryption not decryption.

This is such an amazing video with great explanation.

gracias thanks!

Very good video for explain the HTTPS and the use of certificates, but you didn't spoke of the SSL & TLS? Or all the chain of trust is the SSL/TLS?

This is great. To confirm, the server doesn't request a certificate from the CA for every request - it just renews it every X number of weeks?

tks you

super

Do we also get the CA private key in our browser?

Hi all, I just want to clarify a doubt regarding the chain of trust. In the last example where Baltimore is the root, Cloudflare is the intermediate and hello fresh is the server, the client will finally have 3 sets of public key (1 from root, 1 from intermediate and 1 from server) which it will then use to decrypt the corresponding encrypted public keys attached to each certificate?

You have to give a shout out of the people helping you behind-the-scenes. There's no way you're making all of these videos alone.

Can you make a video how sso and saml works in details also how to setup these in Google

subscribed .

What if you do a man in the middle attack from server to CA and on the same time from the client to the CA and pretend to be the CA. You send back the certificate containing all the information the CA would include together with (your own) public key. Isn't that theoretically possible?

But what will be if MITM sits between facebook server and Certificate Authority and also between our browser and Certificate Authority? He can replace encrypted facebook public key as well as Certificate Authority public key. So our browser can decrypt fake decrypted facebook public key.