#20909: Tor 0.2.9.5-alpha still delivers outdated consensuses -------------------------+------------------------------------------------- Reporter: teor | Owner: Type: defect | Status: new Priority: Medium | Milestone: Tor: 0.2.9.x-final Component: Core | Version: Tor: 0.2.9.5-alpha Tor/Tor | Keywords: regression, must-fix- Severity: Normal | before-029-stable Actual Points: | Parent ID: Points: 1 | Reviewer: Sponsor: | -------------------------+------------------------------------------------- I found one relay on 0.2.9.5-alpha that still has this bug, after scanning about ~400 relays.
{{{ WARNING::Consensus download: 1.8s outdated consensus, expired 44855s ago from snowfall (192.160.102.164:80) 823AA81E277F366505545522CEDC2F529CE4DC3F, max download time 15.0s. }}} https://atlas.torproject.org/#details/823AA81E277F366505545522CEDC2F529CE4DC3F The microdesc consensus is ~12 hours out of date: http://192.160.102.164/tor/status-vote/current/consensus-microdesc The full consensus is fine: http://192.160.102.164/tor/status-vote/current/consensus It was fine yesterday when I scanned it. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20909> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online _______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs