Skip to main content


If you've seen in the PR for #ECH in #curl and been curious what it is? https://github.com/curl/curl/pull/11922

The browsers go all-in on it. Now #Firefox:
https://blog.mozilla.org/en/products/firefox/encrypted-hello/

in reply to daniel:// stenberg://

I've been trying to find proper docs on which approach it would become for a few years now. Good to see that we're getting implementations, so I can go make it and know it won't change from under me.
in reply to daniel:// stenberg://

This is such good news. I've had a plan on ice for a few years now to make it significantly harder to block websites. Excited for this!
Gonna need to find out the state of play with Safari ECH but Chrome/ium + Firefox is more than enough to make it useful.
in reply to Neil Craig

@tdp_org Sadly disabling DOH via use-application-dns.net will also disable ECH, so I'm not sure how much of an improvement this is (specifically in regards to blocking websites)
in reply to daniel:// stenberg://

@tdp_org I totally understand why you need DOH (or DOT etc.), though I do wonder if DNSSEC alone would be enough. But I suppose you could correlate plaintext DNS with the actual request if you wanted to …

And ECH still is a great idea to prevent ISPs from snooping 👍