filmov
tv
SSL/TLS Handshake Process

Показать описание
#ccna #tls #ssl #ccnp #networking #networksecurity #securty
A TLS handshake takes place whenever a user navigates to a website over HTTPS and the browser first begins to query the website's origin server. A TLS handshake also happens whenever any other communications use HTTPS, including API calls and DNS over HTTPS queries.
TLS handshakes occur after a TCP connection has been opened via a TCP handshake.
1.The 'client hello' message: The client initiates the handshake by sending a "hello" message to the server. The message will include which TLS version the client supports, the cipher suites supported, and a string of random bytes known as the "client random."
2.The 'server hello' message: In reply to the client hello message, the server sends a message containing the server's SSL certificate, the server's chosen cipher suite, and the "server random," another random string of bytes that's generated by the server.
3.Authentication: 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.
4.The premaster secret: The client sends one more random string of bytes, the "premaster secret." The premaster secret is encrypted with the public key and can only be decrypted with the private key by the server. (The client gets the public key from the server's SSL certificate.)
5. Private key used: The server decrypts the premaster secret.
6.Session keys created: Both client and server generate session keys from the client random, the server random, and the premaster secret. They should arrive at the same results.
7.Client is ready: The client sends a "finished" message that is encrypted with a session key.
8.Server is ready: The server sends a "finished" message encrypted with a session key.
9.Secure symmetric encryption achieved: The handshake is completed, and communication continues using the session keys.
ABOUT OUR CHANNEL
Our channel is about Technology. We cover lots of cool stuff such as Firewall learning, Tech News and Tech Tutorials
Check out our channel here:
Don’t forget to subscribe!
CHECK OUT OUR OTHER VIDEOS
FIND US AT
GET IN TOUCH
FOLLOW US ON SOCIAL
Get updates or reach out to Get updates on our Social Media Profiles!
A TLS handshake takes place whenever a user navigates to a website over HTTPS and the browser first begins to query the website's origin server. A TLS handshake also happens whenever any other communications use HTTPS, including API calls and DNS over HTTPS queries.
TLS handshakes occur after a TCP connection has been opened via a TCP handshake.
1.The 'client hello' message: The client initiates the handshake by sending a "hello" message to the server. The message will include which TLS version the client supports, the cipher suites supported, and a string of random bytes known as the "client random."
2.The 'server hello' message: In reply to the client hello message, the server sends a message containing the server's SSL certificate, the server's chosen cipher suite, and the "server random," another random string of bytes that's generated by the server.
3.Authentication: 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.
4.The premaster secret: The client sends one more random string of bytes, the "premaster secret." The premaster secret is encrypted with the public key and can only be decrypted with the private key by the server. (The client gets the public key from the server's SSL certificate.)
5. Private key used: The server decrypts the premaster secret.
6.Session keys created: Both client and server generate session keys from the client random, the server random, and the premaster secret. They should arrive at the same results.
7.Client is ready: The client sends a "finished" message that is encrypted with a session key.
8.Server is ready: The server sends a "finished" message encrypted with a session key.
9.Secure symmetric encryption achieved: The handshake is completed, and communication continues using the session keys.
ABOUT OUR CHANNEL
Our channel is about Technology. We cover lots of cool stuff such as Firewall learning, Tech News and Tech Tutorials
Check out our channel here:
Don’t forget to subscribe!
CHECK OUT OUR OTHER VIDEOS
FIND US AT
GET IN TOUCH
FOLLOW US ON SOCIAL
Get updates or reach out to Get updates on our Social Media Profiles!
Комментарии