4 ms·
I think this is phase 1, where phase 2 or 3 is "enabled by default and don't fall back to plain DNS". So it's trivial to defeat until they change a setting. Bu
by peterwwillis 6y ago
I think this is phase 1, where phase 2 or 3 is "enabled by default and don't fall back to plain DNS". So it's trivial to defeat until they change a setting.
But that's not even the big problem here. The big problem is how big an impact this will be on less-than-perfect networks.
The internet feels "snappy" because of DNS's speed and connectionless nature (and a buttload of DNS caching). Once it relies on a connection-oriented protocol, a lot of people's internet experience is going to start sucking badly, and they'll have to modify more of the common internet protocols to make it suck less again.
- new_realist 6y agoWon’t Chrome keep a single connection open for the lifetime of the browser?
- tialaramex 6y agoConveniently DoH servers didn't exist years ago, so any that you're talking to will be new. But new servers have no reason not to implement TLS 1.3, as does Chrome. In TLS 1.3 you can choose to avoid the handshake roundtrip but then you're subject to a replay attack in which any request side effects happen again because your legitimate request was replayed. The bad guys don't get to understand the request or the answer, they just get to perform it, maybe against a different node of a distributed system or in a different timeframe. Conveniently DNS lookups are side effect free so this doesn't matter. So that really cuts down on the potential additional latency compared to even an HTTP GET.