4 ms·
> You're absolutely right, Cloudflare will still see it. That doesn't make this a bad improvement though. You can do something like ECH in a way that not even
by AnthonyMouse 3y ago
> You're absolutely right, Cloudflare will still see it. That doesn't make this a bad improvement though.
You can do something like ECH in a way that not even Cloudflare will see it (it being the connection contents rather than the name, since Cloudflare actually needs the name to route the connection).
The naive way to do it is to do one handshake with Cloudflare that the client uses to provide the "real" name and then another with the "real" server so Cloudflare can't see that. That is possible but then you'd need two handshakes, which is rather inefficient and probably means it wouldn't be used. The interesting question is can someone come up with a way to get that result without the inefficiency.
- YeBanKo 3y ago> You can do something like ECH in a way that not even Cloudflare will see it How is it possible for a Cloudflare to front a website, without knowing what the website it is. You browser is only supposed to do a handshake with a server with a certificate matching the domain, this make Cloudlare in charge of the cert. And Cloudflare needs to forward the traffic to a known location, so they __have__ to know the target host.
- AnthonyMouse 3y agoit being the connection contents rather than the name, since Cloudflare actually needs the name to route the connection
- d-z-m 3y agoSounds kind of similar to [0]. TL;DR: stealth secondary DH key exchange in the nonce field of Client/Server Hello in TLS 1.3. [0]: https://eprint.iacr.org/2023/651.pdf https://eprint.iacr.org/2023/651.pdf