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

Re: [tor-bugs] #2106 [Tor Client]: Controller can't unset httpsproxy if it doesn't resolve

#2106: Controller can't unset httpsproxy if it doesn't resolve
------------------------+---------------------------------------------------
 Reporter:  arma        |          Owner:                    
     Type:  defect      |         Status:  new               
 Priority:  major       |      Milestone:  Tor: 0.2.3.x-final
Component:  Tor Client  |        Version:                    
 Keywords:              |         Parent:                    
   Points:              |   Actualpoints:                    
------------------------+---------------------------------------------------

Comment(by chiiph):

 That hack might work, but what happens when Tor doesn't start for any of
 the other reasons? We may reset the user's super custom config, but it
 failed because the internet was down at that particular moment.
 One idea would be to make it a "two strike" startup, if it fails after the
 reseting, then just fail as usual, but the above problem will remain.

 Another possibility, but on the tor side, would be to signal tor (I'm not
 sure which signals aren't in use) for this special case... But this won't
 work on Windows, right?

 I may be lacking some low level knowledge here, is Vidalia doing something
 wrong when changing from relay to client in terms of controport commands?
 Is this something that can be reproduced through a "plain" controlport
 connection?

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2106#comment:6>
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