[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:
------------------------+---------------------------------------------------
Changes (by mikeperry):
* component: Tor bundles/installation => Tor Client
Comment:
nick - we have no persistent IPC channel between vidalia and Firefox in
order to inform Torbutton of new port pairs. We're using environment
variables for the purpose now..
I think having some way to have Tor either prefer ports, or be smarter
about trying to reusing them is the least-effort most-gain for this
particular issue. Alternatively, maybe Vidalia could be the one who tells
Tor "this was your port from before the restart" using command line
arguments for ControlPort and SocksPort to override the torrc auto options
from disk. The tor manpage says this is possible. Is it a good idea? Is it
the best idea (that doesn't involve new IPC)?
rransom - erinn normally reads Ccs. Also, I still think this is best
solved in the Tor Client or Vidalia. I certainly don't think anything in
the build/packaging is going to solve this.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/4031#comment:8>
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