[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #21273 [Applications/Tor Launcher]: Proxy settings unecessarily limit guard selection process
#21273: Proxy settings unecessarily limit guard selection process
---------------------------------------+-----------------------
Reporter: pastly | Owner: brade
Type: defect | Status: new
Priority: Medium | Milestone:
Component: Applications/Tor Launcher | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
---------------------------------------+-----------------------
Comment (by mcs):
Replying to [ticket:21273 pastly]:
> I can reach any port on through this socks5 proxy. My guard selection is
being artificially limited to guards that have an ORPort of 443.
>
> I suspect that ReachableAddresses should only be set to 80 and 443 if
the proxy type is HTTP(S). Or not at all unless "This computer goes
through a firewall that only allows connections to certain ports" is
checked. In my very limited experience with proxies, it seems sane to
assume only 80/443 for HTTP(S) proxies, but it doesn't seem sane to assume
80/443 for a socks5 proxy.
The rationale for Tor Launcher's behavior came from here:
https://trac.torproject.org/projects/tor/ticket/11405#comment:7
I don't know if "many proxies restrict the set of ports they'll proxy for"
applies to SOCKS5 proxies or not, but the goal was to do something that
would result in a working Tor Browser for most people. You can edit torrc
manually, but the ReachableAddresses settings may be overwritten if you
make changes later using the Tor Network Settings window.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21273#comment:1>
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