[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #19984 [Core Tor/Tor]: Use a better set of comparison/evaluation functions for deciding which connections to kill when OOS
#19984: Use a better set of comparison/evaluation functions for deciding which
connections to kill when OOS
--------------------------+------------------------------------
Reporter: nickm | Owner: nickm
Type: defect | Status: accepted
Priority: High | Milestone: Tor: 0.3.3.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: dos, sockets | Actual Points:
Parent ID: | Points: 2
Reviewer: | Sponsor: SponsorV-can
--------------------------+------------------------------------
Changes (by Hello71):
* priority: Low => High
Comment:
directory connections are poorly impacted by this metric, but:
1. if the connection is legitimate, there will be data flowing down it
soon after fetching directory information anyways. works better with the
new ORPort-only architecture, but for legacy clients I guess we could just
sum together the bandwidth used by an IP address and use that somehow
2. AIUI directory connections are only absolutely necessary during the
very first startup. at any later time, if a directory connection cannot be
made or is suddenly terminated, cached data can be temporarily used until
a connection can be re-established. therefore, prematurely terminating
directory connections is not a huge problem, and is much better than
rejecting new connections which may require relay service.
raising priority as discussed on IRC.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/19984#comment:13>
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