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

Proxy DNS lookups through SOCKS5 possibly broken #112

Closed
ericjung opened this issue Aug 27, 2020 · 3 comments
Closed

Proxy DNS lookups through SOCKS5 possibly broken #112

ericjung opened this issue Aug 27, 2020 · 3 comments
Labels
duplicate This issue or pull request already exists

Comments

@ericjung
Copy link
Collaborator

Sent to me by email:

When a SOCKS5 proxy is enabled, and if DNS over HTTPS in Firefox is turned on, Firefox does not seem to respect if the proxy server handles DNS or not; it will still query DNS through Cloudflare or NextDNS or whatever it's set to in the browser settings, potentially leaking DNS information.

I found this while configuring xxxxxxxxxxxxxx proxy on their servers; using their leak testing tool, it reported I was leaking DNS information. I got the same result while using BrowserLeaks' IP test; even when FoxyProxy was set to using a proxy server, an IP address to Cloudflare was still being queried. When "Enable DNS over HTTPS" in Firerfox's Connection Settings was turned off, neither testing tool showed there were leaks to Cloudflare.

I don't know whether this is a bug in FoxyProxy, a bug in Firefox, or a limitation in how Firefox handles proxy settings, but it seems as though it could be a privacy/security concern.`

I am guessing this is a Firefox bug, but need to confirm. The WebExtensions API is probably not handling this correctly. The work-around is for FoxyProxy to disable DNS over HTTPS when SOCKS5 is used and proxy DNS is selected.

@erosman
Copy link
Collaborator

erosman commented Sep 14, 2022

Subsequent to my reply in above topic, I am also enquiring from Mozilla engineers.

@erosman
Copy link
Collaborator

erosman commented Sep 23, 2023

Is the issue still occurring?

@erosman erosman added the duplicate This issue or pull request already exists label Oct 3, 2023
@erosman
Copy link
Collaborator

erosman commented Oct 3, 2023

Refer to #163

@erosman erosman closed this as completed Oct 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants