ADVERTISEMENT
Google AdSense Slot (headerLeaderboard)
Set your Publisher ID in src/config/ads.ts to display live ads.
Cyber Security Tutorial• 7 min read
HTTPS, TLS 1.3 & Public Key Infrastructure
The TLS handshake, Certificate Authorities (CAs), and preventing Man-in-the-Middle
HTTPS encrypts all communication between browser and server, defending against eavesdropping, tampering, and Man-in-the-Middle (MitM) attacks.
The TLS 1.3 Handshake Workflow
1Client Hello: The client sends supported cipher suites and a key exchange share.
2Server Hello & Certificate: The server sends its digital certificate issued by a trusted Certificate Authority (CA) and its key share.
3Verification: The browser verifies the cryptographic signature of the certificate against trusted root certificates pre-installed in the operating system.
4Symmetric Session Key: Both parties compute a shared symmetric session key using Elliptic-Curve Diffie-Hellman (ECDHE) for rapid bulk encryption.
Pro Tip
TLS 1.3 completes the cryptographic handshake in just 1 round-trip time (1-RTT), down from 2-RTT in legacy TLS 1.2, accelerating page load speeds.
ADVERTISEMENT
Google AdSense Slot (inContentBanner)
Set your Publisher ID in src/config/ads.ts to display live ads.
Test Yourself With Exercise
Who issues and cryptographically signs digital certificates to verify that an HTTPS domain legitimately belongs to its owner?