Комментарии:
I have a question on step 4. How can the web server decrypt the symmetric key shared by the client using their private key?
ОтветитьThanx
ОтветитьHTTTPS
ОтветитьSir - I like your explanation. You break down the problem into simple explanation with very good graphics. Picture speaks thousand words. So true in this case.
ОтветитьI'm so glad I found this channel I don't visit it much but the amount of cool topics I need
Ответитьin the above scenario, are symmetric keys created automatically or we need to create it ? if symmetric keys created automatically , are these created uniquely for every session?
ОтветитьHi sir,
As you said the public key which already installed in our as Root CA will decrypt the certificate which was send by server. By using public we can decrypt private key encrypted data is it possible?
Thankyou. It was crisp and clear explanation of how the keys are exchanged, specifically demonstrating that the confidentiality is achieved using symmetric key
Ответитьperfectly simple & clear thankyou sir
ОтветитьHands down the best explanation I have found anywhere.
Ответитьthanks alott
great
Great explanation :)
ОтветитьThank you ..weather you are a robot or real man you are great teacher..
ОтветитьReally good explanations on the topics.. 👍🏻 thank you!!
ОтветитьThat's really clear and good explanation, thank you very much!
ОтветитьGreat Explanation!!!👌
ОтветитьLike the content! Thanks :)
ОтветитьThank you
ОтветитьGreat job here as always, Sunny!!
ОтветитьHTTTTPS
ОтветитьThe explanation is very easy to understand, eventually I understand how SSL certificate work:)))))
ОтветитьBest explanation i found! Thank you!
Ответитьhi Sunny,
Could you share how we can see where the Google chrome stored some major CAs' authority?
So the client already have a certificate for all the site ?
ОтветитьExcellent!!!!
Ответитьultimate explanation
Ответитьbest explanation
ОтветитьThank you. It's very clear to understand.
ОтветитьReally good and simple explanation. thanks
Ответитьgreat example! really helpful!
ОтветитьHTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTPS
ОтветитьNamaste
Based on domain SSL certificates are classified as three
1. Single Domain - Applicable for only a single domain
2. Wildcard SSL Certificates - Includes subdomains along with the main single domain
3. Multi Domain - Lists multiple domains on one certificate
In terms of strigency of validation these are classified as three
1. Domain validation - This is the least stringent
2. Organization validation - Involves manual vetting process and is more stringent than domain validation
3. Extended validation - Involves full background check of the organization and is most stringent
Thanks
thank you!
ОтветитьThanks a lot for this clear explanation !
I have a question about the case when the client is not a browser (an Api for example). How the Api validate the certificate of the server side ? The client should have somewhere a list of trusted certificate authorities ?
Thank in advance
From the video it is not clear why browser trusts the CA, why the answer can't be faked
ОтветитьAwesome 👍
ОтветитьThanks and when you always said HTTTP made me laugh
Ответитьyou explain so well I am preparing for CompTIA A+ I wish you had all videos compiled in one course like mike i like your explanation and examples
Ответитьyou da man Sunny, thank you
Ответить❤great video🙏
ОтветитьFirst of all sincere Thanks from me, you make fundamentals very simple. Till I watch your video it is difficult but after watching your video the topic becomes much easier. Really excellent genre of teaching.
Ответить🧡
ОтветитьDo this encryption and decryption slow down requests and responses by a server to handle it? As I understood we need to encrypt any of our requests because we don't want to check all the time if this data is sencitive?
ОтветитьWhy the heck does he call it HTTTPS???
ОтветитьPerfect!
Ответить