Closed
Bug 1363342
Opened 7 years ago
Closed 7 years ago
Firefox over proxychains bypasses proxy and reaches the internet directly
Categories
(Core :: Networking, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: Nukeador, Assigned: xeonchen)
Details
(Whiteboard: [proxy][necko-next])
Hi, I've been using Nightly together with proxychains to tunnel the browser connection through a local proxy for a long time now. Just recently nightly updates have broken this and Firefox access the internet directly even when it's run from proxychains. Proxychains config is: socks4 127.0.0.1 9050 Nightly is run by: proxychains /opt/nightly/firefox Every other app keeps working as expected and directing traffic through the proxy, but not Nightly any more. Are there any recent changes that could have influenced in this behaviour? I've tested with clean profiles getting the same problem. Thanks!
Reporter | ||
Updated•7 years ago
|
Summary: Firefox over proxychains bypass proxy and reach the internet directly → Firefox over proxychains bypasses proxy and reach the internet directly
Reporter | ||
Updated•7 years ago
|
Summary: Firefox over proxychains bypasses proxy and reach the internet directly → Firefox over proxychains bypasses proxy and reaches the internet directly
Comment 1•7 years ago
|
||
Gary, is it something you could take a look at?
Assignee: nobody → mmm198219
Whiteboard: [necko-active]
Updated•7 years ago
|
Assignee: mmm198219 → xeonchen
Comment 2•7 years ago
|
||
What platform are you seeing this problem on with Nightly? proxychains is simply a SOCKS4 proxy to Firefox, right? Do you happen know when this problem started for you? Narrowing down the window will help finding the culprit faster...
Assignee | ||
Comment 3•7 years ago
|
||
[1] explains the way how proxychains works, and it probably doesn't work for e10s environment. Would you first try to disable e10s (uncheck "enable multi-process" in preference) and see if it works? If the root cause it not because Firefox doesn't honor the system/browser proxy setting, I'll consider to mark this bug as invalid. A workaround for you is you may choose to use SOCKS4 proxy in the preferences panel and explicitly set to 127.0.0.1:9050. [1] https://github.com/rofl0r/proxychains-ng
Flags: needinfo?(nukeador)
Assignee | ||
Comment 4•7 years ago
|
||
Cervantes, do you know any possibility that we're doing something to prevent Firefox being hooked?
Flags: needinfo?(cyu)
Comment 5•7 years ago
|
||
I am not sure, but preventing LD_PRELOAD hooks doesn't sound likely. I suggest checking this under gdb to find out whether the proxychains-ng functions are taking effect in the parent process.
Flags: needinfo?(cyu)
Assignee | ||
Comment 6•7 years ago
|
||
I cannot reproduce this bug on Nightly 2017-06-05 64-bit Linux, proxychains 3.1 proxychains.conf: socks4 127.0.0.1 9050 # Tor connect to https://check.torproject.org/ and it shows I'm configured to use Tor. Rubén, can you still reproduce this bug?
Reporter | ||
Comment 7•7 years ago
|
||
You are right, latest nightly is working correctly and connections are traveling through the proxy.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(nukeador)
Resolution: --- → FIXED
Reporter | ||
Comment 8•7 years ago
|
||
Apparently the issue is back since yesterday's build.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 9•7 years ago
|
||
I still cannot reproduce this Rubén, is this reproducible in another clean platform?
Flags: needinfo?(nukeador)
Whiteboard: [necko-active] → [proxy][necko-next]
Assignee | ||
Comment 10•7 years ago
|
||
No sufficient information to handle this bug, I'm going to close this until we have more info.
Status: REOPENED → RESOLVED
Closed: 7 years ago → 7 years ago
Flags: needinfo?(nukeador)
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•