Re: [tor-bugs] #10968 [Tor]: Authorities should use past consensuses to assign relay flags

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

#10968: Authorities should use past consensuses to assign relay flags
------------------------+--------------------------
     Reporter:  asn     |      Owner:
         Type:  task    |     Status:  new
     Priority:  normal  |  Milestone:  Tor: 0.2.???
    Component:  Tor     |    Version:
   Resolution:          |   Keywords:  tor-auth
Actual Points:          |  Parent ID:
       Points:          |
------------------------+--------------------------

Comment (by arma):

 Which flags did you have in mind here?

 For the Guard flag (#11328), I think we definitely want consensus values,
 not votes. The question is actually "what fraction of the past interval
 was this relay choosable?" If one authority thought it was choosable but
 the others didn't, then it wasn't.

 I think Fast is more subjective and not dependent on history (it's about
 speed, not stability, but see #11327 for how they should listen to the
 consensus if they don't have their own opinion about speed).

 Running is also subjective and not based on past history.

 For HSDir, I could totally see an argument for using recent consensus
 values.

 For Stable, it's about whether it has restarted. We look for restarts by
 seeing a descriptor with an unexpected uptime, or by failing three
 reachability tests in a row. I guess if we wanted we could change this to
 either looking for an unexpected uptime, or seeing whether there's ever a
 consensus where it's missing the Running flag -- an hour is approximately
 three reachability tests, give or take.

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