Opened 3 years ago

Last modified 8 weeks ago

#3948 new enhancement

"fooport auto" should be able to get a hint

Reported by: arma Owned by:
Priority: major Milestone: Tor: 0.2.6.x-final
Component: Tor Version:
Keywords: tor-client Cc: erinn, alan.hamlett@…
Actual Points: Parent ID:
Points:

Description (last modified by arma)

In #3945 we learned that "socksport auto" (as implemented in #3076) on Windows is confusing users who use external applications that expect Tor to be listening on port 9050. The "fix" was to disable using auto ports in the TBB 0.2.2 Windows bundles.

A better answer to this issue is to

A) teach Tor how to remember which port it used last time, and try that one first (#3511)

B) seed it with our favorite port, e.g. by setting another config option like "SocksPortPreferred 9050". Maybe it would try both the preferred port and the one it picked last time, in some order. My first thought is that it should try the previous one first, and fall back to the configured preference before falling back to a random high-numbered port.

If we want to get fancier, we could make the prefered list be a 'schedule' of ports to try, e.g. for ORPortPreferred it could be "443,80".

Picking a more normal port should also help the Comodo firewall users in #3941 who are being blocked from reaching their high-numbered port.

Child Tickets

Change History (9)

comment:1 Changed 3 years ago by arma

  • Cc erinn added

comment:2 Changed 3 years ago by nickm

Part (A) above is, I think, the same as bug #3511.

comment:3 Changed 3 years ago by arma

  • Description modified (diff)
  • Summary changed from "fooport auto" should be able to get a hint, and should try to pick a consistent port to "fooport auto" should be able to get a hint

Right you are! Pruning this one so it is more clearly part (B).

comment:4 Changed 2 years ago by nickm

  • Milestone changed from Tor: 0.2.3.x-final to Tor: 0.2.4.x-final

Too tricky and fragile to be workable for 0.2.3 imo.

comment:5 Changed 2 years ago by ahamlett

  • Cc alan.hamlett@… added

This is related to #4182.

comment:6 Changed 19 months ago by nickm

  • Keywords tor-client added

comment:7 Changed 19 months ago by nickm

  • Component changed from Tor Client to Tor

comment:8 Changed 15 months ago by nickm

  • Milestone changed from Tor: 0.2.4.x-final to Tor: 0.2.5.x-final

comment:9 Changed 8 weeks ago by nickm

  • Milestone changed from Tor: 0.2.5.x-final to Tor: 0.2.6.x-final
Note: See TracTickets for help on using tickets.