3 ms·
TCP SYN is not encrypted, and neither is Client Hello. Even with TCP cookies and TLS session resumption, the initial packet is still unencrypted, and can be int
by simiones 1y ago
TCP SYN is not encrypted, and neither is Client Hello. Even with TCP cookies and TLS session resumption, the initial packet is still unencrypted, and can be intercepted.
- haiku2077 1y agoClient Hello can be encrypted: https://support.mozilla.org/en-US/kb/understand-encrypted-client-hello https://support.mozilla.org/en-US/kb/understand-encrypted-cl...
- EE84M3i 1y agoYes but this still depends on identity. It's not unauthenticated.
- ekr____ 1y agoThe situation is actually somewhat more complicated than this. ECH gets the key from the DNS, and there's no real authentication for this data (DNSSEC is rare and is not checked by the browser). See S 10.2 [0] for why this is reasonable. [0] https://tlswg.org/draft-ietf-tls-esni/draft-ietf-tls-esni.html#name-unauthenticated-and-plainte https://tlswg.org/draft-ietf-tls-esni/draft-ietf-tls-esni.ht...
- simiones 1y agoOh, right, thanks for the correction! However, ECH relies on a trusted 3rd party to provide the key of the server you are intending to talk to. So, it won't work if you have no way of authenticating the server beforehand the way GP was thinking about.