[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #10762 [TorBirdy]: TorBridy should try both SOCKS port 9050 and 9150
#10762: TorBridy should try both SOCKS port 9050 and 9150
-----------------------+-------------------------
Reporter: mikeperry | Owner: ioerror
Type: defect | Status: new
Priority: normal | Milestone:
Component: TorBirdy | Version:
Keywords: | Actual Points:
Parent ID: | Points:
-----------------------+-------------------------
TorBridy's SOCKS configuration should try both 9050 and 9150 and use the
one that works.
You can crib Torbutton's local tor check here (which requires access to
the control port):
https://gitweb.torproject.org/torbutton.git/blob/master:/src/chrome/content/torbutton.js#l1701
We wrap that with the option to fall back to the remote check if
transproxy is set here:
https://gitweb.torproject.org/torbutton.git/blob/master:/src/chrome/content/torbutton.js#l1675
The remote check is here:
https://gitweb.torproject.org/torbutton.git/blob/master:/src/chrome/content/torbutton.js#l1770
Unfortunately if you perform any network activity (including a remote tor
check) with a socks port set, you may run into #8511, causing any hosts
you contact to become unreachable after you change SOCKS settings. I am
not sure if that caching behavior is present in Thunderbird too. The local
tor check won't be affected by this bug, though.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10762>
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