3 ms·
TLS 1.3 has a 0rtt handshake, which is pretty baller. It's just not widely deployed. And it likely won't be. 0RTT Allows for replay attacks (I capture you
by valarauca1 9y ago
TLS 1.3 has a 0rtt handshake, which is pretty baller.
It's just not widely deployed.
And it likely won't be. 0RTT Allows for replay attacks (I capture your packets, and replay them). Without a round trip this will always exist.
Also 0RTT is only for re-connections not initial connections.
The solution is only like 0RTT be executed once and only once, but this isn't part of TLSv1.3 and is waiting to _globally_ approved. Until then nobody smart will touch it.
---
0RTT is only supported by Cloud-Flare and Google. Cloud-Flare makes you track 0RTT yourself so a fair number of sites are insecure. Google does SSL tick synchronization across data centers because their arrogant and is extremely vulnerable to timing att-
- jopsen 9y agoWouldn't 0RTT be safe for GET requests that doesn't contain cookies or private data? Granted I suppose such interpretation would have to be done by browsers. And even then it could be used to figure out which site you are visiting.
- valarauca1 9y agoYou are assuming * The TLS connection is instantly closed after the GET ends * A new 0RTT ticket isn't created * No session information is transmitted (most GET's even have session information for ads/metrics).