@@laithacademy Hahahaah am I reading it right, fcc asks laith to post on their channel wow.. 😅 I think only you and Craig Dennis (my two favorite teachers, what a coincidence) had such a honor to be asked directly by fcc themselves to host on their channel..
@@laithacademyby the way laith I think you're the right guy to ask this question as it seems you've lots of experience in different fields according to your videos on this UA-cam channel.. So an intermediate front end developer freelancer I'm pondering whether i should apply as front end intern or move to learn devops cloud infrastructure and then trying to get an intern job in that field, or maybe go all the way to LLM, machine learning, ai and build a few projects in that field and apply as intern there.. I've interests and curiosity in all the 3 topics I just can't decide which path should I take further haha ... So maybe you can suggest me as a mentor your valuable opinion regarding all that? Thanks again and keep sharing all those awesome valuable videos
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.
Why do we encrypt the hashes in the first place if the public key is also available so an attacker can also easily decrypt the hash? Even the attacker won't be able to alert the certificate, but why do we go through encryption?
@@falconx7560 To check if the certificate of a given site was signed by a trusted CA. At first, you cannot trust the site you are visiting, that it is the site you want to visit. You need someone third party, whom you trust, who will confirm that this site is the site. Someone who will issue a certificate to this site. This third party is the CA (certificate authority), a kind of 'notary' for electronic certificates, whom we trust (or rather browsers and operating systems). The CA encrypts the hash of the applicant certificate with its private key and adds it to the certificate as a digital signature. And only with the public key of this CA, can this hash be correctly decrypted. If you try to decrypt with a different key - the hash will always be different, incorrect, never will match to the certificate hash calculated during checking. So if you decrypted the correct hash, using the correct public key, you know that it was encrypted with the private key of this CA. Only this CA holds its private key, no one else has it. This is what gives us the certainty that the site's certificate was signed by a trusted, legal, exactly this one CA. What gives us the certainty that the site's certificate is definitely assigned to this domain, to this site you are visiting - the CA ensures this. So from now on you can trust the website you are visiting and you can start exchanging SSL keys to encrypt the communication between you and the website.
@@falconx7560 To verify that a site's certificate has been signed by a trusted CA. To begin with, you can't trust the site you are accessing that this is the site you want to visit. You need a third party you trust to certify that this site is that site. Someone who will issue a certificate to that site. That third party is the CA (certificate authority), a sort of 'notary' for electronic certificates that we trust (and more so browsers and operating systems). The CA encrypts the applicant's certificate digest with its private key and adds it to the certificate as a digital signature. And only with this CA's public key can this digest be decrypted correctly. If you try to decrypt with another key - the digest will always be different, incorrect, it will never match the certificate digest calculated during the check. So if you have decrypted a corrected hash, using the correct public key, you know that it was encrypted with the private key of that CA. Only that CA holds its private key, no one else does. This gives us confidence that the site certificate was signed by a trusted, legitimate, exactly that one CA. Which gives us confidence that the site certificate is definitely assigned to that domain, to that site you are visiting - the CA provides. So from now on, you just trust the site you're visiting, and you can start exchanging SSL keys to encrypt the communication between you and the site.
@@falconx7560being able to decrypt is not the point. It's not about confidentiality but rather it's about authenticity. If a man in the middle changes the content of the file, he can also calculate a new hash with the same algorithm and replace the hash. So now if you calculate the hash, it matches. But the file is altered. Now let's suppose the hash is encrypted using the private key. A man in the middle changes the content of the file. He calculates a new hash. But now he needs to encrypt the new hash with the private key which he doesn't have. Now you can decrypt the hash using the public key and compare it with the calculated hash and verify that the data isn't modified
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.
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 UA-cam 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!
This is absolutely an amazing video. There is one small thing that may be missed by viewers and that is why we are using asymetric encryption to encrypt a symetric key. Why not just use asymetric encryption the whole time? Why do we need to validate a symetric key? The reason is because asymetric encryption/decryption is a computationally expensive operation compared to symetric encryption/decryption. The majority of the data transfer happens with symetric encryption with a key which both the client and sever agree upon, all this crazy asymetric infrastructure is there in order to verify the symetric key was not tampered with. Thanks for this video!
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!
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
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.
This is an EXCELLENT video on this. I have an Associates degree in cybersecurity & digital forensics (and one in network admin), and still couldn't wrap my mind around this. I also have purchased a 200$ course in cryptography (and it's an excellent course with visuals and labs that I haven't completed cuz it's about 40hrs long). This gets to the basics in about 40min. Love it. One thing I'm still trying to understand is how the shared secret keys are derived and exchanged after verification of authority of the server certificate.
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.
first time I went beyond simply exposing myself to jargon and understood the logic. That's 2 and a half pages of notes, including a drawing of my own. Tops best spent time this week, even though earlier I launched my first ever website with its own API. Thank you
5:05 honestly? with how complicated and insanely fast it is, the fact that we fed lightning to a rock and taught it to think for us as well as communicate through invisible wavelengths to other rocks? basically magic tbh
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!
@@jay_wright_thats_rightOr he is a technical person, with exposure to other parts of the vast thing that is the IT world. You could program compilers your entire life and not need to understand these concepts.
One of the best explanations and breakdowns I have seen. Fantastic video, thank you Mr.Laith Academy. This video a must for anyone studying or working in Cybersecurity.
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.
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.
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.
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 !!!
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.
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.
This is one of the best videos I have come across this 2024...simple and detailed explanation...Do you have hands on videos on renewing certificate? "Not secure"
when i first clicked this video, does it really need 40 minutes to explain this concept? HOWEVER, this is the video that really helps you understand this concept. Thank you for a great video!
I love your video and your explanation especially when you are explaining certain nuances about this process. Awesome vid/explanation I'll look forward to more of these kinds of vids.
27:26 The server-side exchange with the authority is not a subprocess of the connect handshake, but a one-time prologue for getting the signed certificate, where the domain name is an essential entry of the certificate.
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.
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.
I love your teaching style. Do you have interest in sharing one of your already made courses with our channel?
Responded on LinkedIn
That will be amazing we will gladly watch it ,what an amazing combo
@@laithacademy Hahahaah am I reading it right, fcc asks laith to post on their channel wow.. 😅 I think only you and Craig Dennis (my two favorite teachers, what a coincidence) had such a honor to be asked directly by fcc themselves to host on their channel..
@@laithacademyby the way laith I think you're the right guy to ask this question as it seems you've lots of experience in different fields according to your videos on this UA-cam channel.. So an intermediate front end developer freelancer I'm pondering whether i should apply as front end intern or move to learn devops cloud infrastructure and then trying to get an intern job in that field, or maybe go all the way to LLM, machine learning, ai and build a few projects in that field and apply as intern there.. I've interests and curiosity in all the 3 topics I just can't decide which path should I take further haha
... So maybe you can suggest me as a mentor your valuable opinion regarding all that? Thanks again and keep sharing all those awesome valuable videos
would 100% listen to this guy on freecodecamp he does an awesome job
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.
Why do we encrypt the hashes in the first place if the public key is also available so an attacker can also easily decrypt the hash? Even the attacker won't be able to alert the certificate, but why do we go through encryption?
@@falconx7560 To check if the certificate of a given site was signed by a trusted CA.
At first, you cannot trust the site you are visiting, that it is the site you want to visit. You need someone third party, whom you trust, who will confirm that this site is the site. Someone who will issue a certificate to this site. This third party is the CA (certificate authority), a kind of 'notary' for electronic certificates, whom we trust (or rather browsers and operating systems).
The CA encrypts the hash of the applicant certificate with its private key and adds it to the certificate as a digital signature. And only with the public key of this CA, can this hash be correctly decrypted. If you try to decrypt with a different key - the hash will always be different, incorrect, never will match to the certificate hash calculated during checking. So if you decrypted the correct hash, using the correct public key, you know that it was encrypted with the private key of this CA. Only this CA holds its private key, no one else has it. This is what gives us the certainty that the site's certificate was signed by a trusted, legal, exactly this one CA. What gives us the certainty that the site's certificate is definitely assigned to this domain, to this site you are visiting - the CA ensures this.
So from now on you can trust the website you are visiting and you can start exchanging SSL keys to encrypt the communication between you and the website.
@@falconx7560 To verify that a site's certificate has been signed by a trusted CA.
To begin with, you can't trust the site you are accessing that this is the site you want to visit.
You need a third party you trust to certify that this site is that site. Someone who will issue a certificate to that site. That third party is the CA (certificate authority), a sort of 'notary' for electronic certificates that we trust (and more so browsers and operating systems).
The CA encrypts the applicant's certificate digest with its private key and adds it to the certificate as a digital signature. And only with this CA's public key can this digest be decrypted correctly.
If you try to decrypt with another key - the digest will always be different, incorrect, it will never match the certificate digest calculated during the check. So if you have decrypted a corrected hash, using the correct public key, you know that it was encrypted with the private key of that CA. Only that CA holds its private key, no one else does. This gives us confidence that the site certificate was signed by a trusted, legitimate, exactly that one CA. Which gives us confidence that the site certificate is definitely assigned to that domain, to that site you are visiting - the CA provides.
So from now on, you just trust the site you're visiting, and you can start exchanging SSL keys to encrypt the communication between you and the site.
@@falconx7560being able to decrypt is not the point. It's not about confidentiality but rather it's about authenticity.
If a man in the middle changes the content of the file, he can also calculate a new hash with the same algorithm and replace the hash. So now if you calculate the hash, it matches. But the file is altered.
Now let's suppose the hash is encrypted using the private key. A man in the middle changes the content of the file. He calculates a new hash. But now he needs to encrypt the new hash with the private key which he doesn't have. Now you can decrypt the hash using the public key and compare it with the calculated hash and verify that the data isn't modified
-> Make a better video.
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.
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 UA-cam 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!
Accidentally clicked on this video, but after nearly an hour of watching, what I got was satisfaction. You're doing a great job! Thanks!
This is absolutely an amazing video. There is one small thing that may be missed by viewers and that is why we are using asymetric encryption to encrypt a symetric key. Why not just use asymetric encryption the whole time? Why do we need to validate a symetric key? The reason is because asymetric encryption/decryption is a computationally expensive operation compared to symetric encryption/decryption. The majority of the data transfer happens with symetric encryption with a key which both the client and sever agree upon, all this crazy asymetric infrastructure is there in order to verify the symetric key was not tampered with.
Thanks for this video!
thank you, this is exactly what I was wondering while watching
Great addition.
Came to comments to say the same thing
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!
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
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.
This is an EXCELLENT video on this. I have an Associates degree in cybersecurity & digital forensics (and one in network admin), and still couldn't wrap my mind around this. I also have purchased a 200$ course in cryptography (and it's an excellent course with visuals and labs that I haven't completed cuz it's about 40hrs long). This gets to the basics in about 40min. Love it. One thing I'm still trying to understand is how the shared secret keys are derived and exchanged after verification of authority of the server certificate.
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.
This is the best video I have ever viewed on this topic. What a brilliant explanation. Thank you for putting this material together.
This is probably the BEST tutorial i have ever watched
first time I went beyond simply exposing myself to jargon and understood the logic. That's 2 and a half pages of notes, including a drawing of my own. Tops best spent time this week, even though earlier I launched my first ever website with its own API. Thank you
So far best explanation I've seen! Explained like a I'm five years old
5:05 honestly? with how complicated and insanely fast it is, the fact that we fed lightning to a rock and taught it to think for us as well as communicate through invisible wavelengths to other rocks? basically magic tbh
Never seen such a great tutor... you made this very simple.. live long and happy! Deserves 10000000000000$
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!
No they don't, you're just not a technical person.
@@jay_wright_thats_rightOr he is a technical person, with exposure to other parts of the vast thing that is the IT world.
You could program compilers your entire life and not need to understand these concepts.
Beautifully explained, i had no idea about certificates, and this video has moved me further in some understanding! Thank you
One of the best explanations and breakdowns I have seen. Fantastic video, thank you Mr.Laith Academy.
This video a must for anyone studying or working in Cybersecurity.
The one of the best video I have ever seen on UA-cam Thank you so much for making it very clear❤❤❤ Best wishes
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.
The best explanation on the topic. Kudos for the remarkable effort you have put in! ❤
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!
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.
One of the best, concise and most completed videos i have seen, its a brain refresh
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.
I Understand encryption better now this is a good video explaining asymmetric and symmetric encryption
I truly enjoyed the video because of the ability of the trainer the explain things so well. Kudos to the Laith Academy & the trainer
THANK YOU SO MUCH!!!!!!! This is the best explanation I found on TSL!!! Thank you!!!!!
Very clear, Detailed enough to understand. Thank you for the quality of teaching
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 !!!
Too good ! For years I couldn't figure out how Public/Private keys work..until this video
Great video about ssl I ever seen on internet 👍
I have an exam tomorrow, and I skip security lessons. This video is a lifesaver! Thanks you!
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.
extremely clear explanation. easy to follow even without much previous experience
Very nice explanation, not just useful, but also well detailed and visualised
Thank you for your efforts
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.
Bro, you explained the thing that I spent too much time too understand in about 50 minutes. Thanks
Crazy explanation ❤❤❤ in an hour I am attending client round I am 200% confident right now
Awesome video. The best one I ever saw till date
at 22:32 minutes I fully understand how secure communication happened at the first place !!! Awesome work as you do always Love from Pakistan
super, excellent, very good explanation. very good teacher
Thanks for detailed explanation ,Best ever explanation i have come across FOR SSL HTTP AND HTTPS❤
This is one of the best videos I have come across this 2024...simple and detailed explanation...Do you have hands on videos on renewing certificate? "Not secure"
you are one of the best teachers out there i really appreciate you and your work.
Really wonderful video. simple to understand and a detailed explanation helped me a lot.
Amazing knowledge and super content. Great Job!!
meticulously detailed and well explained most noble sire.
incredible, amazing, so easy to understand. some people have that talent of explaining stuff so good.
Thanks for the great explanation of a complex process...I finally have a better understanding of the whole process!
when i first clicked this video, does it really need 40 minutes to explain this concept? HOWEVER, this is the video that really helps you understand this concept. Thank you for a great video!
Best explanation I’ve seen.
I love your teaching style and you are explained everything consicely. thank you so much... LAITH
This is the best explanation of Cryptography concept, Thank you so much for making this.
I’m only about 10 minutes in, but I can already say I really like how you explain things 😀
Very well explained.. Appreciate your good work. 👏👏
very nice and simple explanation for a critical concept. Thanks a lot
I loved your video, it explained me a lot and always made me think of how it works while you were explaining. ❤
One of the best and detailed video video ,so amazing explanation ❤
Thanks a lot for making this video. Helped me understand clearly how the complex process of encryption works
I love your contents sooooooooooooooo much! I love your teaching style. Please make more tutorials!
one of the best ones ever, excellent explanation.Thanks
The best explanation I have come across on this topic! 🙌
You made my Every Topics very clear. Thankyou so much
I love your video and your explanation especially when you are explaining certain nuances about this process. Awesome vid/explanation I'll look forward to more of these kinds of vids.
Great explanation Laith thanks a lot for sharing your efforts !!!
Well I really love your teaching style :)
When go slow and to the detail you actually saved my time ;) one of the best learning videos on youtube.
Superb video on https. Thanks for the elaborate, clear explanation.
AMAZING video really this has to be the best explaniation on that topic i have ever seen
Best video on SSL certificate on any platform.. thank you so much!! You just earned a subscriber :)
Thanks for your effort in making this video. It is easy to understand and I really like it.
Thanks so much; this is the best explanation I have found 👍
Finally... I understood this concept thanks to you...
You are such an amazing teacher!!
Amazing video, thank you for such labor to make it for people who doesn't really know all this stuff
Thanks for your pedagogy, I really appreciated your video.
Thank you for such crisp and structured flow. This helped a lot!!
27:26 The server-side exchange with the authority is not a subprocess of the connect handshake, but a one-time prologue for getting the signed certificate, where the domain name is an essential entry of the certificate.
Sick video mate. Really well explained, great depth! Pedagogical dream 😊
Great video ans love your presentationand teaching method, keep it up
You just earned yourself a gold star ⭐️ for the day !
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.
Excellent job. Very nice explanation.
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.
completed !!! to be honest never seen such a wonderful explanation on such complex topic
Regard: Kim from Pakistan
Very clear, explained very well.
Wow that's a lot of job to go to all those details, thanks for this i like to have all those details that was hard to find.
Thank you so much for taking the time to explain this.
Informative information
One of the best explanations
Great content! I thoroughly enjoyed your explanation; it was simple and easy to understand. Keep up the fantastic work!
Thanks a lot Laith Academy... great stuff and very well explanation.
It's finally starting to make some sense, thanks for explaining!
just watched your nginx course, you're really good at explaining man!
definitely gonna watch more of your videos
Great Video.Thanks for your Time and Effort.It really helps.