Encrypted Client Hello
I'm not seeing it. It looks contradictory what they're saying.<p>> This means that whenever a user visits a website on Cloudflare that has ECH enabled, no one except for the user and the website will be able to determine which website was visited.<p>But if you look at the inner/outer SNI part:<p>> The outer SNI is a common name that, in our case, represents that a user is trying to visit an encrypted website on Cloudflare. We chose cloudflare-ech.com as the SNI that all websites will share on Cloudflare. Because Cloudflare controls that domain we have the appropriate certificates to be able to negotiate a TLS handshake for that server name.<p>> The inner SNI contains the actual server name that the user is trying to visit. This is encrypted using a public key and can only be read by Cloudflare. Once the handshake completes the web page is loaded as normal, just like any other website loaded over TLS.<p>So Cloudflare sees it? That's definitely not the same as what they're describing, it's more of a wink-wink Applesque "trust me bro" style  of "privacy" - a consolidation of traffic under the pretext of something else.<p>I also looked at the draft document they linked, and that seems to match up with what I'm understanding.<p>> If ECHClientHello.type is outer, then the server acts as a client-
      facing server and proceeds as described in Section 7.1 to extract
      a ClientHelloInner, if available.