Open Bug 783178 Opened 12 years ago Updated 2 months ago

socks_remote_dns=true leaks DNS (in some conditions)

Categories

(Core :: Networking: Proxy, defect, P3)

14 Branch
x86_64
Linux
defect

Tracking

()

UNCONFIRMED

People

(Reporter: lzdn, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-backlog][proxy])

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:14.0) Gecko/20100101 Firefox/14.0.1
Build ID: 20120713225548

Steps to reproduce:

Firefox 14.0.1 x64 Linux
I was testing socks5 proxy + DNS resolving with wireshark.

Test method:
0. Change proxy, exit firefox and launch firefox again;
1. Open wireshark and start capture on eth adapter;
2. Enter 'dns' in filter bar;
3. In firefox, navigate to any url, repeat several times;
4. Stop capture and check the result.
   There should be not dns packet for previous visited urls.

Settings:
Only one socks5 proxy is set.
network.proxy.no_proxies_on: doesn't include 127.0.0.1, or the remote socks5 server
network.proxy.socks_remote_dns=true
network.prefetch-next=false


Actual results:

With proxy=127.0.0.1:port, DNS always leaked.
With proxy=remote-domain:port, DNS leakage was not observed.


Expected results:

socks_remote_dns=true doesn't leak DNS.
Component: Untriaged → Networking
Product: Firefox → Core
Severity: normal → major
This sounds like the same problem identified in bug 751465.
Whiteboard: [necko-backlog]
See Also: → 458303
Whiteboard: [necko-backlog] → [necko-backlog][proxy]
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
QA Whiteboard: qa-not-actionable

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.

Severity: major → --
Blocks: necko-proxy
Severity: -- → S3

Moving bug to Core/Networking: Proxy.

Component: Networking → Networking: Proxy
You need to log in before you can comment on or make changes to this bug.