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

Re: [tor-bugs] #4031 [Tor Client]: Firefox fails to find SOCKS proxy after tor is restarted through Vidalia

#4031: Firefox fails to find SOCKS proxy after tor is restarted through Vidalia
------------------------+---------------------------------------------------
 Reporter:  rpw         |          Owner:  nickm   
     Type:  defect      |         Status:  assigned
 Priority:  normal      |      Milestone:          
Component:  Tor Client  |        Version:          
 Keywords:              |         Parent:          
   Points:              |   Actualpoints:          
------------------------+---------------------------------------------------

Comment(by nickm):

 It's not about CC; it's about component.  I get *all* trac emails, and
 generally don't the ones that are for software I don't work on.  If you
 label something as a vidalia bug, or a TBB bug, I will assume that chiiph
 or helix is taking care of it.

 On to the bug:

 If Tor can pick a new socks port when it restarts (and it is allowed to if
 you say "socksPort auto"), then it seems to me that vidalia or whatever
 restarts tor needs some way to tell firefox about it.

 Now, there's a good argument that Tor should try harder to re-use the same
 port as it used last time... and that's something I'd like to implement.
 But with SocksPort auto, there is no way to guarantee that at all.

 So if we're using socksport auto, and Tor restarts, we need to be able to
 tell everything that cares about the new socksport.

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