3 ms·
> the imminent ESNI standard has that one covered, too. Too slow, I'm afraid. Word on the street is that any hello containing ESNI will be blocked from day one
by Hizonner 5y ago
> the imminent ESNI standard has that one covered, too.
Too slow, I'm afraid. Word on the street is that any hello containing ESNI will be blocked from day one in too many places for it to ever get traction, including all of China. I believe draft ESNI is blocked by the GFOC today.
To even have a chance of making ESNI/ECH widespread, you'd have to make it mandatory for all TLS. That wouldn't fly politically in the working group, because the "enterprise" people have at least some influence there, and they want to do exactly the same kinds of DPI that North Korea would want to do. Even if it came out mandatory on the standards track, it would probably still fail at this point.
It might have worked if it'd been mandatory in TLS 1.2 or even TLS 1.3, but it seems too late now.
We'll see if they also disrupt DoH to the point of making it unusable. I bet they at least give it a try.
- josephcsible 5y agoIf Microsoft, Apple, and Google all agreed to make ECH mandatory on the same future date, wouldn't that basically force the hands of every other enterprise?
- zarzavat 5y agoThe goal of ESNI is not to bypass China's intranet. The goal is to say to DPI countries such as the UK: either you implement a China-style great firewall or you implement a free internet. There is no middle ground where you can spy on people without it being obvious.
- tialaramex 5y ago> That wouldn't fly politically in the working group, because the "enterprise" people have at least some influence there, and they want to do exactly the same kinds of DPI that North Korea would want to do. If this was true, TLS 1.3 would have RSA kex. The "enterprise" people (specifically in fact EDCO, the Enterprise Data Centre Operators, Nalini Elkins' group) really wanted to keep RSA kex. It was removed in TLS 1.3 anyway because it's a bad idea. In practice the intention is that ECH will be GREASEd, so yes, it will go from being nowhere to being apparently everywhere almost overnight. It's not specifically intended that GREASing ECH will defy the Great Firewall, but it's a possible outcome. China can decide its own policies without help from us. For EDCO and similar outfits, ECH changes nothing.
- Hizonner 5y ago> If this was true, TLS 1.3 would have RSA kex. I hope you're right... > In practice the intention is that ECH will be GREASEd If even fake ECH extensions get rejected, then it's hard to deploy the whole GREASy burrito. > China can decide its own policies without help from us. ... but China can make it uncomfortable to support ECH worldwide. It's not a free action for a service to risk being blocked in China, or for client software to accept being unreliable or unusable in China. That affects deployment in the rest of the world. We'll see who wins the war of wills, but I'm afraid that the "Western" entities that have the most control over what's widely deployed are not going to have will enough.
- pas 5y agoAny "service" that wants to support China needs to have serious presence there anyway.
- shawnz 5y agoThey actually are recommending for everyone to add fake ESNI/ECH data even if you don't intend to use ESNI/ECH. See: https://datatracker.ietf.org/doc/html/draft-ietf-tls-esni#section-10.9.4 https://datatracker.ietf.org/doc/html/draft-ietf-tls-esni#se...