[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #7694 [Tor]: Handle WSAEADDRINUSE more nicely
#7694: Handle WSAEADDRINUSE more nicely
-------------------------+--------------------------------------------------
Reporter: bastik | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Tor: unspecified
Component: Tor | Version:
Keywords: tor-client | Parent:
Points: | Actualpoints:
-------------------------+--------------------------------------------------
Comment(by bastik):
I assume that it was and still is a good idea to prevent users from
shooting them in their own foot. (If 9050 would have been taken by another
application data might end-up on unexpected location) So better kill Tor
than let this happen.
Instantly I like the per-listener approach, while the global should be
quicker to implement and use.
I wonder how much of an edge-case this actually is. Only people that run
relays/bridges and TBB at the same time could be affected. (Or people
running multiple Tor instance, which might be not that common; or when the
port is taken by another process, which should not be case for TBB since
you try to set it to auto)
The bridge runs whenever the computer will be on long enough and provides
port 9001 for non-browsing traffic. When I don't expect to be on long
enough I don't start the bridge and run TBB instead, which provides 9050
(browsing if needed) and 9001 for non-browsing traffic.
Since Tor Browser won't operate outside the TB-Bundle I can't use it with
the bridge. I have to launch a second instance of Tor (the one from TBB)
When the bridge is running and I launch TBB, I expect port 9001 to be
taken, but don't care.
Honestly I don't know how rare the ports-in-use case is and how much
effort it is to code a solution. Anyway, the ticket doesn't hurt.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7694#comment:3>
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