Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is ESNI enabled by default when using DoH? #941

Closed
35609902357 opened this issue Sep 28, 2019 · 9 comments
Closed

Is ESNI enabled by default when using DoH? #941

35609902357 opened this issue Sep 28, 2019 · 9 comments

Comments

@35609902357
Copy link

No description provided.

@35609902357 35609902357 changed the title Is ESNI enabled by default when using a DoH server? Is ESNI enabled by default when using DoH? Sep 28, 2019
@ghost
Copy link

ghost commented Sep 29, 2019

No my friend, DoH does not encrypt SNI header.

DOH_TEST

Please stay safe!

@35609902357
Copy link
Author

How can ESNI be enabled in dnscrypt-proxy? Is there a line to write in dnscrypt-proxy.toml?

@jedisct1
Copy link
Member

@35609902357
Copy link
Author

@jedisct1 A bug from Firefox does not address the point. So supposedly dnscrypt-proxy should encrypt SNI by default (even though ESNI checker by CloudFlare doesn't display it), but the image posted by @mkirisame shows SNI is actually unencrypted.

@jedisct1
Copy link
Member

ESNI doesn't exist yet, it's still being designed.

What exists is an early experiment by Cloudflare and Mozilla, that turned out to be a good marketing tool. The web browser decides whether to enable this or not.

Right now, the rule hardcoded in Firefox is "enable it only if Firefox was configured to directly talk to Cloudflare DNS, and the user tries to connect to a Cloudflare customer".

The linked issue is not a bug. It's about an intentional limitation.

@uBlock-user
Copy link

#622 (comment)

@Mikaela
Copy link

Mikaela commented Oct 1, 2019

It can actually be enabled in Firefox by setting network.security.esni.enabled;true in about:config, but you have to use a DNS-over-HTTPS provider (that doesn't have to be Cloudflare, while that is the only one Firefox ships with). https://bugzilla.mozilla.org/show_bug.cgi?id=1542754#c3 is another bug worth mentioning.

@jedisct1
Copy link
Member

jedisct1 commented Oct 1, 2019

You don't have to just use a DNS-over-HTTPS provider. You have to configure Firefox to do the resolution itself, bypassing all system settings.

@35609902357
Copy link
Author

@Mikaela I'm aware of it, I was hoping to have it at router level to serve all clients. Thank you for pointing it out, and thank you @jedisct1 for your work and @mkirisame for the test. And thank you too @uBlock-user, I read that comment already, but I thought it was just an issue with Cloudflare's website.

@DNSCrypt DNSCrypt locked and limited conversation to collaborators Oct 31, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants