Re: [tor-bugs] #28458 [Core Tor/sbws]: Stop resolving domains locally and stop using non-exits as 2nd hop

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#28458: Stop resolving domains locally and stop using non-exits as 2nd hop
---------------------------+--------------------------------
 Reporter:  juga           |          Owner:  juga
     Type:  defect         |         Status:  needs_revision
 Priority:  Medium         |      Milestone:
Component:  Core Tor/sbws  |        Version:  sbws: 1.0.0
 Severity:  Normal         |     Resolution:
 Keywords:                 |  Actual Points:
Parent ID:                 |         Points:
 Reviewer:                 |        Sponsor:
---------------------------+--------------------------------

Comment (by juga):

 Replying to [comment:9 teor]:

 > But what happens when the exit that's being measured fails?

 if the exit is the one being measured (1st hop) is treated as any other
 relay,
 it stores the result as error, it'll get measured in the next
 prioritization loop, which gives less priority to the relays that failed.
 A new exit is chosen for every relay that gets measured, so the next time
 that the relay that failed gets measured will get an exit with similar
 bandwidth at random.

 > Do we need to give it a 50% chance of being measured like a non-exit?

 i don't understand what you mean as "non-exit", all relays are measured as
 non-exits (1st hop), the exits are chosen independently for the 2nd hop.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28458#comment:10>
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