SSL, TLS, HTTPS Explained

[@igwejk]

An important point that's worth mentioning, otherwise the server-hello phase would be insecure, the client and server both have a trusted authority they could rely on for authenticating each other. The client verifies the server's SSL certificate with the certificate authority that issued it. This confirms that the server is who it says it is, and that the client is interacting with the actual owner of the domain.

[@brucewayne2480]

Yes because a certificate authority verified a domain owner and signed its data with its private key, that signature is included in the certificate , and the public key of known certificate authorities are stored in the browser

[@lanyloh9876]

I was wondering about this. Thank you!

[@lawrencedoliveiro9104]

The client has a list of CA certs that it trusts, so it will accept any server cert that is signed by one of them. TLS can also be used for two-way authentication. Also for secure communication between different parts of your own organization, you can create your own CA cert and install that at the endpoints so they can trust each other.

[@alexandermiasoiedov6637]

How does the server know that the client is not the hacker that sits in the middle? Namely, how does the server knows that session_key is authentic and generated by the client, but not by the hacker in the middle?

[@igwejk]

@@alexandermiasoiedov6637 The man in the middle should not be capable of decrypting the client's message.

[@barbobrien9318]

Comprehensive and easy to understand. The best part is that the video was short!

[@miehaga7444]

I love the audience of this channel, very polite, graceful and intellectual.

[@ashu7pathak]

Thanks.

[@ReflectionOcean]

HTTPS is HTTP + TLS (Transport Layer Security) TLS is a handshake process between the client and server with asymmetric encryption to exchange a session key used for Data Transmission with symmetric encryption.

[@noorzanayasmin7806]

is the key the SSL certificate verified by Certificate Authority?

[@faultboy]

You also watched the video? Interesting!

[@geeksified]

@@noorzanayasmin7806 ​ SSL cert is the certificate you bought from your hosting or anywhere you bought it from, which contains the public key, and when you create your csr, you will be given with the verified private key that can only be paired with your public key.

[@PannasastraSR]

Your explanation is easy to understand than watch the video

[@nikhil182]

Good summary of the video!

[@danielkrastev6786]

Best animation aesthetics ever. Pure joy to watch.

[@cassianocampes]

Direct to the point, clean, and easy to understand. Great content!

[@SantoshKumari-d8r]

I love how the audience effectively participating in Comments Sharing knowledge. That's the beauty of well educated environment.

[@mouhssineannouri5497]

The session key isn't directly swapped between the client and server, even with asymmetric encryption. Instead, they exchange a random string of bytes, often referred to as a 'pre-master secret' or 'nonce', which serves as the basis for generating the session key on both ends using the algorithms previously agreed upon in the cipher suite exchange.

[@يعقوبالدويك]

yo my moroccan bro can we contact thru fb or ig or whatsapp?

[@lemonade2345-j4e]

I can tell that you are a scientist. Wouldn't surprise me if you had a PHD. Really an articulate presentation with virtually no flutter. A rare sight on YT.

[@NitroBrewbell]

The easiest explanation of a complex topic ever done in less than 6 mins !

[@asn65001]

I like that you didn't mention TLS 1.1 and below. No need to teach something that's going out the door. And thanks for pointing out the ciphers. In teaching others about TLS, I've found ciphers to be the hardest concept for people to grasp.

[@jackscalibur]

I think that everyone needs to understand the ciphers involved, but most people aren't going to be concerned with the technical details of the cryptographic algorithms.

[@ameyapatil1139]

This was so so helpful straight to the point ! Worth every second ❤

[@goldfishbrainjohn2462]

Ordered your both system interview books, volume 1 and 2. Can't wait to read the books!

[@siddharthamohan6382]

Are the books worth it?

[@goldfishbrainjohn2462]

@@siddharthamohan6382 Definitely.

[@cybrainx72]

You missed the phase where Client has to validate is Certificate is signed by the trusted CA.

[@alaakhaleel9137]

Thank you bro, as my father always said, clean and easy, I want your room clean and attitude easy.

[@ivanmatveev4313]

Amazing!! The best video about HTTPs, I ever seen before!

[@magic_pink_horse]

You're the best presenter for this kind of stuff!

[@helgarudersleben480]

bytebytego team, i would like to thank you for your videos - they are not only illustrated really well, they are really informative!

[@patricknelson]

Bravo. 👏 This is a very succinct high level explanation. I’m already somewhat familiar with the handshake, but this does a fantastic job summarizing things in an approachable fashion without diving into too much detail. Great thing is, there’s still plenty more to dive into as well and this provides a well structured guide on how to do that.

[@javalisidda7983]

🎉

[@nishantdalvi9470]

Yeah even I was confused about the how does certificate check and key exchange serially happens this video cleared my doubt

[@anshumansahu8476]

It is very nice and clean exlaination without messing up terminology..great job

[@ARMOTISARMOTIS]

it was really great fast and everything important was in this video thank you I watched more than 7 videos and put more than 1 hour to find you :) Thanks I understood everything clearly :)

[@SimpleLivingHigherThinking]

Awesome video short ,clear , easy to understand thank you !!! 😀

[@EricRodriguez-uu6gj]

You are very professional with your videos and your teaching; is a suggestion you should do a video with an A.I voice

[@itscheckmate878]

Best explanation I found on utube about TLS and ssl

[@Djsanddy]

short and sweet tutorials really loving your channel

[@rembautimes8808]

Excellent channel, well illustrated. A must watch for those in tech risk like me

[@EbonySeraphim]

Along with the top comment here, I think it is helpful to understand that step #2 Certificate Check involves the client cross referencing that the DNS name they resolved matches the hostname presented on the server's certificate. Otherwise, the TLS handshake will (appropriately) fail because even though the server certifcate may be valid and trusted, the server presenting it is not truly associated with it.

[@hanshima_]

Wow... that is important and helped me today. I was having some problems with a broker and was receiving invalid IP error.

[@Passersby98]

Bro's animation and explaination are superb. 👍

[@vitordeoliveira6139]

question: Diffie-Hellman (DH) is used for key exchange, the client and server exchange public keys and use them to generate a shared secret key that is used for symmetric encryption. Yes he share a public key also...

[@misteroy9]

Exactly, that's also my surprise he said it doesn't transfer the public key over the network. @ByteByteGo could you explain it?

[@tatianamarinmarulanda6958]

Love ALL your videos and channel! You rock!!!

[@tesla1772]

great explantion and to the point. also tls 1.3 solves forward secrecy problem of tsl1.2

[@oah8465]

hands down, you nailed it.

[@jeffg4686]

one of the best videos for overview on this.

[@skytechbits]

Love the cool channel name. Thanks for the great info.

[@johnw.8782]

As always, great job. Looking forward to the next book.

[@bala007raju]

so nicely explained , Thanks lot , Glad I found this video and channel . thanks again

[@simranjeetsingh8864]

Thank you, you explain it very well

[@user-yz7ts2fq9m]

wow, great and clear explanation! Thank you very much!

[@shamfervans2452]

Great content. Simply explained

[@mcab2222]

perfect straightforward. love it

[@NadaII]

Your content is fantastic. Thank you.

[@rezafebrian4733]

Wow very nice explanation 🎉

[@andreadiotallevi5780]

Thank you - beautifully explained!

[@wwhill8033]

Excellent explanation!! Thanks

[@adilhashmi7608]

clean and easy to understand thanks for this one

[@bestcuts4745]

Beautifully explained. Classy video. Keep creating. !!!

[@thndesmondsaid]

Thanks for the video. I think you could have explained more about what TLS and SSL are specifically, but thanks for explaining in detail how HTTPS works.

[@thebesttechnical3608]

Very informative video. Thanks

[@sbj0880]

Very well explained - I love how soothing and insightful it is to go through your videos. How do you record these videos..curious? Thank you.

[@munteanionut3993]

Thanks a lot! This is very useful! 03:47 it s hard to follow due to -I think- you using indefinite artical "a" (as in "a symmetric") vs the way "asymmetric" is pronounced. Also the fact that you added "symmetric encryption" to the diagram AFTER you mentioned your point. Sorry for nit-picking, just hope this would help anyone else

[@ricp]

Great expalantion, thanks!

[@unique_ruler_memes3003]

And one more main reason for not using symmetric key is : When server sends the public key only to the client. Not the private key.. so the client only can encrypt the data using public key it has received with the certificate, not able to decrypt any data came from the server. Thats why we use seasion key exchange..

[@stephenh9483]

"Client Hello" LOL hilarious. Computers really do appreciate kindness

[@MrJaved123]

Fantastic explanation.. Thank you

[@lensimonchang]

very clear elaboration and good sharing!, Appreciate!

[@JJVee427]

Simple, very well explained, thank you!

[@ait-bendaoudmohammed9262]

5:30 about diffie hellman I think you wanted to say "Without ever transmitting over the network the private key" the public key is of course shared using a trusted CA...

[@yash1152]

4:41 >_"as with most optimizations; it's a bit harder to explain"_ glad go be reminded of it (:

[@ovidiuandrei6013]

Very good explanation. Thanks man !

[@QueeeeenZ]

HTTPS is not a protocol technically, it is a scheme. The protocols used are actually called HTTP and TLS.

[@siddharthsorout3446]

bytebytego team, i would like to thank you for your videos , really informative!

[@s.m.hconstantin3887]

incredible video That helped me a lot Thanks

[@rodolfocabralneves8279]

Does the client create a private key and share it with the server in the key exchange process?

[@behrad9712]

Thank you very much!🙏👌

[@chriseddisford1834]

Excellent video! Very well explained.

[@prashanthb6521]

This is excellent explanation.

Very nice visuals!

[@juanmayen21]

Thanks so much for this video.

[@hemanthkumartirupati]

Excellent explanation

[@venkybabu8140]

Public keys were trapped sometimes and that's why no public keys travel. Mostly by NAT re-config. SSL means a set of algorithms accepted between with certificate means that the binary coded files used for decryption. Key means algorithm. Why public and private keys means that public used for encryption of the algorithm of choice and private is end to end algorithm transfer and use. About a thousand algorithm exchanges for a single transaction. So don't try.

[@ilromape]

very nice explanation. Thx

[@aquarius2642]

Wonderful video explaining the internal working of SSL TLS. This got me wondering that about what other questions related to HTTPS SSL TLS do web developers need to know the answers to to be able to do their jobs. I doubt they need the internals of how HTTPS SSL TLS work. Web developers just need to understand 1. Libraries that enable http requests and responses - client side and server side. 2. What are the steps in getting a certificate 3. what sort of attack are prevented through this kind of encryption 4. what are the libraries objects methods that enable https on both client side and server side 5. what are the steps relevant to setting up https tls and ssl on self hosted and cloud hosted servers

[@nicolepierce2517]

Very interesting need to know

[@Mandrickgmaing3]

Thanks man. Good lesson

[@hjxy2012]

Thank you. And how do you draw these magic architecture pictures?

[@zhujunwang1667]

Really good one! Thanks a lot!

[@Bobbel888]

1:03 Assymetric encryption alone can be proxied, at least in cases ECC and RSA. Where does the protocol prevent a man-in-the-middle attack ?

[@zixuanzhao6043]

DH alone is prone to man-in-the middle attack. So the certification verification is vitally important which the video doesn't cover much. Basically the server send a signature which is some private-key encrypted digestion of server identity information. The client then verify the public key through chain-of-trust by layers of authorities that issue certifications (system root authority is trusted unconditionally unless your local system is messed up). Using the verified public key the client decrypt the signature and compare the result to the digest generated through the negotiated digest/hash algorithm. If everything checks out, the server identity is trusted because only the private key owner is able to generate that signature.

[@davidmoody2470]

Great video, thanks.

[@lucasguaru]

I have a question. When this hand shake happens? It does for the first request and keep this connection stablished for the next calls or it does for every request? Im having difficult to imagine it if we have clusters, if the connection is kept alive.

[@caiohenrique5587]

How do you make those video animations ?

[@Art-kz6zf]

How does the client identify itself in the subsequent requests in the phase 4? Does the server need to keep in memory all the thousands of client specific session keys?

[@vincat84]

great video! thanks!!

[@algovec4024]

Great video thank you!

[@rl6382]

Sir.... how does your channel NOT HAVE 20M SUBS???!?!?!?!

[@pjchender]

This is super clear! Thank you!

[@aidataverse]

Very useful information

[@danish6192]

Great, just please add Certificate Verification as well

[@hlexjava]

Question - so if we have private key. We can decrypt tcpdump file?

[@jhfyt0539]

amazing explanation

[@pramithasdhakal5367]

Is not storing the session key on client side, e.g. browser, unsafe?

[@shortest-nerdev-eugene]

I have a question about TCP Connection while client surfing the web site. As I understood, when client connect to the web server as a first time, then the task, as the video explained, will be proceeded between client and server side. After once the client & the server release their connection, TCP Close, Is the client and the server have to re-proceed the progress? Or the client just can use the exist Asymmetric & Symmetric keys?

[@SeviersKain]

I never wanted to understand those trivial details until I came across developing my own softwares...these things should be taught coherently together, not separately...

[@maruthuk]

Brilliant!👍

[@itskarthickm]

May I know which tool that you used for the Illustration or to make the presentation? It is simply impressive and easy to understand..

[@tonycheung5532]

great video

[@niuhe]

clear and helpful👋

[@mahamadoutogola4001]

Thank you 😊

[@ruthwikd311]

Great explanation , but please be loud next time

[@smashit002]

@bytebytego - recently i faced an issue while onboarding a Thanos sidecar (aws account) instance into my Thanos querier (different aws account). The logs showed that the Thanos endpoint cert is from LetsEncrypt and the ThanosQueries is from Route53. Due to it being LetsEncryt it does not recognize the cert authority. How tk fix this?