How HTTPS Handshake Happens
sudhakar.online
How HTTPS Handshake Happens
1–10 of 96 posts
Re: How HTTPS Handshake Happens
#2There are some really cool "tricks" for avoiding the round trip — round trips are why everyone should be using a global load balancer for SSL. Clients have to send 2 packets across the world and wait for a reply, which can add >100ms before any actual work happens.
http2 helps because you can multiplex a bunch of requests into a single connection, less waiting on new connections to be established.
TLS 1.2 with session resumption lets clients reuse existing sessions after the first connection.
TLS 1.3 has a 0rtt handshake, which is pretty baller. It's just not widely deployed.
Re: How HTTPS Handshake Happens
#3There are some really cool "tricks" for avoiding the round trip — round trips are why everyone should be using a global load balancer for SSL. Clients have to send 2 packets across the world and wait for a reply, which can add >100ms before any actual work happens. http2 helps because you can multiplex a bunch of requests into a single connection, less waiting on new connections to be established. TLS 1.2 with sessio…
0rtt is only for resuming sessions. I believe the first handshake won't be any faster with 1.3. Still neat.
Re: How HTTPS Handshake Happens
#4There are some really cool "tricks" for avoiding the round trip — round trips are why everyone should be using a global load balancer for SSL. Clients have to send 2 packets across the world and wait for a reply, which can add >100ms before any actual work happens. http2 helps because you can multiplex a bunch of requests into a single connection, less waiting on new connections to be established. TLS 1.2 with sessio…
Any idea when TLS 1.3 will be supported in NGINX? What browsers support it as well?
Re: How HTTPS Handshake Happens
#5Genuinely curious, as HTTPS is something I do not fully understand even with this simplification:
If the browser's symmetric key is encrypted with icicibank's public key, why can't a sniffer unlock it by also requesting icicibank's public key and decrypting the key sharing message?
Re: How HTTPS Handshake Happens
#6Genuinely curious, as HTTPS is something I do not fully understand even with this simplification: If the browser's symmetric key is encrypted with icicibank's public key, why can't a sniffer unlock it by also requesting icicibank's public key and decrypting the key sharing message?
Only the private key can decrypt it. This is the difference between asymmetric and symmetric encryption algorithms.
Re: How HTTPS Handshake Happens
#7There are some really cool "tricks" for avoiding the round trip — round trips are why everyone should be using a global load balancer for SSL. Clients have to send 2 packets across the world and wait for a reply, which can add >100ms before any actual work happens. http2 helps because you can multiplex a bunch of requests into a single connection, less waiting on new connections to be established. TLS 1.2 with sessio…
Any idea when TLS 1.3 will be supported in NGINX? What browsers support it as well?
The problem is not in Nginx part, you must wait for TLS 1.3 implementation in OpenSSL, LibreSSL, etc.
Re: How HTTPS Handshake Happens
#8Genuinely curious, as HTTPS is something I do not fully understand even with this simplification: If the browser's symmetric key is encrypted with icicibank's public key, why can't a sniffer unlock it by also requesting icicibank's public key and decrypting the key sharing message?
The payload is encrypted with the bank's public key but it can only be decrypted with their private key. This is the basis of public key cryptography [1].
Re: How HTTPS Handshake Happens
#9Genuinely curious, as HTTPS is something I do not fully understand even with this simplification: If the browser's symmetric key is encrypted with icicibank's public key, why can't a sniffer unlock it by also requesting icicibank's public key and decrypting the key sharing message?
you can encrypt with public key, but it cant be decrypted with same key. its assymetric encryption.
Re: How HTTPS Handshake Happens
#10Genuinely curious, as HTTPS is something I do not fully understand even with this simplification: If the browser's symmetric key is encrypted with icicibank's public key, why can't a sniffer unlock it by also requesting icicibank's public key and decrypting the key sharing message?
Public Key encryption is like a bank deposit box.
Anyone can encryption (put things in), but only the Private Key (the bankers) can decrypt (see whats inside).