Opened 14 years ago

Last modified 7 years ago

#247 closed defect (Not a bug)

Tor doesn't seem to work with Network configuration

Reported by: dedwards Owned by:
Priority: High Milestone:
Component: Core Tor/Tor Version: 0.1.0.16
Severity: Keywords:
Cc: dedwards Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Running OS X 10.3.9 with Tor installed; Network settings pointing to Privoxy on 127.0.0.1, port 8118 for HTTP,
HTTPS, and Gopher. Using Safari 1.3, Camino 1.0b1 and Firefox 1.5 with SwitchProxy and the browser's Connection
settings pointing to Privoxy as well.

Connecting to ipid.shat.net/ using Safari or Camino shows an ip address in a different part of the country or
world, as expected. Using Firefox 1.5 with SwitchProxy turned off (Network settings for OS X are still enabled), I get an
ip address for my ISP, even though they're not running any Tor servers. If I use Network Utility to do a Whois lookup,
it also says I'm coming from my ISP; same if I go to www.dnsstuff.com (Java and JavaScript are off). Turning on SwitchProxy
(even while Network settings are enabled) and trying again gets me an IP address in a different part of the country or world,
as it should be.

This makes no sense, and it doesn't inspire confidence, since I get different results depending on which browser I'm using.
I followed the directions for installation and setup, so I can only presume it's a bug of some sort, perhaps with OS X, or Tor.

[Automatically added by flyspray2trac: Operating System: OSX 10.4 Tiger]

Child Tickets

Change History (3)

comment:1 Changed 14 years ago by arma

Only Apple applications use the network-wide socks configuration.

Firefox ignores it.

I would suggest that if you want to make sure each application is using socks, then
you should configure that application.

I agree that it doesn't inspire confidence -- I'm not convinced that OS X's idea
for a network-wide socks configuration was a smart one, but I am convinced that
their execution was not good.

But I'm going to close this as not-a-bug, since there isn't really anything Tor can
do about it.

comment:2 Changed 14 years ago by arma

flyspray2trac: bug closed.

comment:3 Changed 7 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.