SSL, TLS, HTTPS Explained
Vložit
- čas přidán 16. 05. 2024
- To get better at system design, subscribe to our weekly newsletter: bit.ly/3tfAlYD
Checkout our bestselling System Design Interview books:
Volume 1: amzn.to/3Ou7gkd
Volume 2: amzn.to/3HqGozy
ABOUT US:
Covering topics and trends in large-scale system design, from the authors of the best-selling System Design Interview series.
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.
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
I was wondering about this. Thank you!
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.
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?
@@alexandermiasoiedov6637 The man in the middle should not be capable of decrypting the client's message.
Direct to the point, clean, and easy to understand. Great content!
I really appreciate the content. Simple and insightful.
Comprehensive and easy to understand. The best part is that the video was short!
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.
is the key the SSL certificate verified by Certificate Authority?
You also watched the video? Interesting!
@@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.
Your explanation is easy to understand than watch the video
Good summary of the video!
bytebytego team, i would like to thank you for your videos - they are not only illustrated really well, they are really informative!
Best animation aesthetics ever. Pure joy to watch.
You're the best presenter for this kind of stuff!
It is very nice and clean exlaination without messing up terminology..great job
As always, great job. Looking forward to the next book.
I love the audience of this channel, very polite, graceful and intellectual.
Thanks.
Ordered your both system interview books, volume 1 and 2.
Can't wait to read the books!
Are the books worth it?
@@siddharthamohan6382 Definitely.
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.
🎉
Yeah even I was confused about the how does certificate check and key exchange serially happens this video cleared my doubt
This was so so helpful straight to the point ! Worth every second ❤
Best explanation I found on utube about TLS and ssl
perfect straightforward. love it
Simple, very well explained, thank you!
Amazing!!
The best video about HTTPs, I ever seen before!
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.
Excellent video! Very well explained.
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.
great explantion and to the point. also tls 1.3 solves forward secrecy problem of tsl1.2
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 :)
short and sweet tutorials
really loving your channel
Beautifully explained. Classy video. Keep creating. !!!
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.
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.
Excellent explanation!! Thanks
one of the best videos for overview on this.
so nicely explained , Thanks lot , Glad I found this video and channel . thanks again
incredible video
That helped me a lot Thanks
wow, great and clear explanation! Thank you very much!
Excellent channel, well illustrated. A must watch for those in tech risk like me
Fantastic explanation.. Thank you
Hi,
In your System-Design PDF, one of the reasons to switch to symmetric encryption was mentioned this:
"Security: The asymmetric encryption goes only one way. This means that if the server tries to send the encrypted data back to the client, anyone can decrypt the data using the public key."
Is this statement correct? If yes, can you please explain?
very clear elaboration and good sharing!, Appreciate!
hands down, you nailed it.
beautifully presented. well done keep up the good work my friend
This is super clear! Thank you!
Very good explanation. Thanks man !
clean and easy to understand thanks for this one
Really good one! Thanks a lot!
Could you tell us how you create the video animations?
Thank you. Great video!
Great expalantion, thanks!
Thanks man. Good lesson
This is excellent explanation.
Brilliant!👍
If public keys are sent to the client, can this be exported somewhere and then the middle-man then creates his own request with a fully verified client cert (supposing the device was "forcefully" verified the domain it's targeting to)?
May I know which tool that you used for the Illustration or to make the presentation? It is simply impressive and easy to understand..
Sir, what graphics software do you use for making your videos? Your illustrations are so good!
Thanks so much for this video.
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?
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...
Exactly, that's also my surprise he said it doesn't transfer the public key over the network.
@ByteByteGo could you explain it?
Great video thank you!
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?
very nice explanation. Thx
Please, does anyone knows what is the simulations program?
Thanks!
And thank you for the video, outstanding explanation.
Great video, thanks.
one question, is rsa used to generate the session key ?
Thank you brother
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.
great video! thanks!!
the animation looks great. which tool do you use?
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.
Excellent explanation
Very interesting need to know
Thank you very much!🙏👌
Very useful information
Very nice visuals!
Can the above listed communication between client and server. Can it be seen in something like wireshark? If yes could an example be shown?
4:41 >_"as with most optimizations; it's a bit harder to explain"_
glad go be reminded of it (:
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.
clear and helpful👋
Thank you.
Thanks for information
Here server means Load balancer- correct? There might be 100s of hosts running behind load balancer. Does client establish connection to one of those hosts or the front facing load balancer?
SSL, TLS, and HTTPS are all cryptographic protocols used to ensure secure communication over the internet. They play a crucial role in protecting sensitive data transmitted between a client (such as a web browser) and a server. Let's explain each of these terms:
SSL (Secure Sockets Layer):
SSL is an older cryptographic protocol that was initially developed by Netscape in the 1990s. It was widely used to provide secure communication over the internet, especially for websites handling sensitive information like login credentials or credit card details. However, due to security vulnerabilities and weaknesses found in SSL, it has been largely deprecated and replaced by its successor, TLS.
TLS (Transport Layer Security):
TLS is the successor to SSL and was introduced as a more secure and robust cryptographic protocol. It operates at the transport layer of the internet communication stack and ensures secure data transmission between a client and a server. TLS uses a combination of symmetric and asymmetric encryption algorithms to establish a secure connection. The latest version of TLS at the time of writing is TLS 1.3, which has further improved security and performance over previous versions.
HTTPS (Hypertext Transfer Protocol Secure):
HTTPS is not a separate protocol but rather a combination of HTTP and TLS (or SSL in older implementations). It is the secure version of the standard HTTP protocol used for transmitting data between a client's web browser and a web server. When a website uses HTTPS, it means that the data exchanged between the client and the server is encrypted using TLS or SSL, ensuring that it cannot be intercepted or tampered with by unauthorized parties.
When a user connects to an HTTPS-enabled website, the following steps occur:
The client (web browser) sends a request to the server, indicating that it wants to establish a secure connection using HTTPS.
The server responds with its SSL/TLS certificate, which contains the server's public key and other details.
The client verifies the authenticity of the certificate by checking its validity and whether it is signed by a trusted Certificate Authority (CA).
If the certificate is valid, the client and the server perform a handshake to negotiate the encryption algorithm and establish a secure connection.
Once the secure connection is established, all data transmitted between the client and the server is encrypted and secure from eavesdropping or tampering.
In summary, SSL and TLS are cryptographic protocols used for secure communication, with TLS being the more modern and secure version. HTTPS is the combination of HTTP and TLS (or SSL) and is used to ensure secure data transmission over the internet, especially for sensitive information. Enabling HTTPS on websites is crucial for protecting user data and ensuring a safe browsing experience.
LMFAO, did you really just get chatgpt to give you the answer? 💀
Thank you. And how do you draw these magic architecture pictures?
I got very confused around the start of step three when you were saying "a symmetric" and "asymmetric" a lot hehe
Perfect !
HTTPS is not a protocol technically, it is a scheme. The protocols used are actually called HTTP and TLS.
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.
Thanks Lam
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
Love the videos. What software do you use to make the video animations?
i have the same exact question..These animations are so clean
@@mario_luis_dev In some other videos, it is mentioned that He uses Adobe Illustrator or some other adobe product.
What tool are you using to present the tutorial? Very nice 👍
Question - so if we have private key. We can decrypt tcpdump file?
bytebytego team, i would like to thank you for your videos , really informative!
Awesome!
Am I correct in saying TLS1.3 uses Symmetric encryption for key exchange since DH is symmetric?
How do you make those video animations ?
great video
i think TLS 1.2 is the best version currently as 1.3 has a security vulnerability in its supply chain (one of its dependencies that is unique to the version i believe). This is according to recent software engineering daily podcast with guest Ilkka Turunen
in this video which version did he explained 1.2 or 1.3
How you create these content animations?
Can you give us some details about that?
which animation software you used to create this video?
I have 2 doubts
1. which public key and private key is known as assymetric keys .on server under .ssh present keys or ssl keys
2. Secure data trasmission between client and server using client symmetric key or
client will use server public key for encryption which will decrypt by server private key and server will use client symmetric key for encryption which will decrypt by client symmetric key
For 2nd question -
a) AES, DES or similar algorithms are used for generating the session key (secret key ; symmetric key)
b) This session key is then encrypted using the server's public key got from the digital certificate.
c) The server on receiving this, decrypts it using its private key.
d) Now, the client and the server have the session key.
Hi, thanks for your videos, very helpful. I'm writing my master thesis and I'm looking for a way to compare TLS cipher suites about their computational cost. My main idea is about counting number of operations and related weigth for each algorithm in every cipher suites, but I can't find any information about these metrics or just a tool to implement RSA (e.g.) and understand the computational weigth, in order to compare the main cipher suites. Can you or anyone else give me any input to implement this metric? Many thanks
awesome!
Question: how could client decrypt data sent by server? If private key is only in server??
Once the exchange is done, then both the client and the server have a copy of the same symmetric key that they can both use to encrypt data. This is the yellow box in the diagram.
I meant: How can the data coming from the server to the client be decrypted? How can the client decrypt this data if only the private key is on the server? @@alastairtheduke
once I close the browser tab is the TLS handshake ends? or TCP handshake ends? or what will happen? When does TCP and TLS handshake ends
May I know what tools do you use to create this animation? Thanks!