[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #4663 [Tor Client]: Tor proxy settings bypassed when proxy is down/broken

#4663: Tor proxy settings bypassed when proxy is down/broken
---------------------------+------------------------------------------------
    Reporter:  DasFox      |       Owner:          
        Type:  defect      |      Status:  assigned
    Priority:  major       |   Milestone:          
   Component:  Tor Client  |     Version:          
  Resolution:              |    Keywords:          
      Parent:              |      Points:          
Actualpoints:              |  
---------------------------+------------------------------------------------

Comment(by cypherpunks):

 Replying to [comment:19 cypherpunks]:
 > Replying to [comment:18 arma]:
 > > Just to be clear, has anybody confirmed that setting the Httpsproxy
 torrc option does not allow any proxy bypass by Tor? We're all assuming
 that the original bug reporter just got confused by Vidalia's (bad)
 interface.
 >
 > I've replicated similar behaviour using Tor v0.2.2.35 and Vidalia 0.2.17
 where Tor ignores the configured proxy settings entirely. This only seems
 to affect a Windows XP SP3 machine.
 >
 > The XP machine is in front of a firewall which only permits a proxy
 access to the network. Therefore all attempts for this machine to download
 the directory are expected to fail. It must make results using the proxy
 for successful connection.
 >
 > However when configuring a HTTP\HTTPS proxy - Tor simply ignores the
 settings and attempts to go direct. Logging doesn't seem to report
 anything suspicious. I think it's a Tor issue as configuring torrc with
 'HTTPProxy' and running Tor direct also has the same issue.
 >
 > Can confirm Tor goes direct since PCAP shows SYN packets to various
 directory IP's (unanswered of course). My question - how can force Tor to
 use its configured proxy?
 >
 > Thanks :) John Payne

 After re-reading, it seems adding 'HTTPSProxy' allows Tor to connect via
 the proxy, and everything seems tunnelled successfully (it's a Blue Coat
 ProxySG, so only accepting CONNECT methods on port 443, and SSL
 interception disabled). It seems if Vidalia wrote HTTPSProxy, that would
 solve the problem :)

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/4663#comment:20>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs