socks_remote_dns=true leaks DNS (in some conditions)

UNCONFIRMED
Unassigned

Status

()

Core
Networking
P3
major
UNCONFIRMED
6 years ago
7 months ago

People

(Reporter: lzdn, Unassigned)

Tracking

14 Branch
x86_64
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

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

(Reporter)

Description

6 years ago
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.
(Reporter)

Updated

6 years ago
Component: Untriaged → Networking
Product: Firefox → Core
(Reporter)

Updated

6 years ago
Severity: normal → major

Comment 1

6 years ago
This sounds like the same problem identified in bug 751465.
Whiteboard: [necko-backlog]

Updated

a year ago
See Also: → bug 458303
Whiteboard: [necko-backlog] → [necko-backlog][proxy]
You need to log in before you can comment on or make changes to this bug.