[tor-bugs] #20501 [Core Tor/DocTor]: Scan 0.2.9.x relays to see if they're serving an out-of-date consensus?

Mon Oct 31 19:31:57 UTC 2016

#20501: Scan 0.2.9.x relays to see if they're serving an out-of-date consensus?
-----------------------------+------------------------
 Reporter:  arma             |          Owner:  atagar
     Type:  enhancement      |         Status:  new
 Priority:  Medium           |      Milestone:
Component:  Core Tor/DocTor  |        Version:
 Severity:  Normal           |     Resolution:
 Keywords:                   |  Actual Points:
Parent ID:                   |         Points:
 Reviewer:                   |        Sponsor:
-----------------------------+------------------------

Comment (by rubiate):

 Would you be able to repeat the scan for the microdesc consensuses?
 (armadev asked me on #tor-dev to ask). There are definitely relays that
 have a perfectly valid normal consensus but a stale microdesc consensus,
 and I think the microdesc consensus being out of date is a more prevalent
 issue (and I'm told a bigger issue because more clients use them).

 The best (worst?) example I found is this one:

 > 7BB160A8F54BD74F3DA5F2CE701E8772B841859D (0.2.9.3-alpha): currrent

 It's microdesc consensus was valid-until 2016-09-28 22:00:00

--
Ticket URL: <https://trac.torproject.org/ticket/20501#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online