When the valid consensus is old but still barely valid, are the descriptors referenced in it still valid?

If the answer is "no", then that might explain why the dirauths are now getting bombarded with traffic while we haven't had a valid consensus in > 18h. Also relevant to ideas extending the validity of consensuses

changed milestone to %Tor: unspecified

added component::core tor/tor milestone::Tor: unspecified priority::very high resolution::not a bug severity::normal status::closed tor-dirauth type::defect labels

Trac:
Keywords: N/A deleted, tor-auth added

Trac:
Component: Tor Directory Authority to Tor

Trac:
Milestone: Tor: unspecified to Tor: 0.2.5.x-final
Priority: normal to critical

So, microdesc validity is "for a week after it was last listed." Microdescs can't be at fault here.

routerinfo_t validity is complicated; there's a lot of code that checks its published_on field. ROUTER_MAX_AGE is 48 hours, so might not be at fault, though we might have a rule to never prune a routerinfo_t in our current consensus if we don't have one. There are about 10 places that look at the 24-hour ROUTER_MAX_AGE_TO_PUBLISH, though, and I wonder whether all of them are correct.

Trac:
Milestone: Tor: 0.2.5.x-final to Tor: 0.2.???

Milestone renamed

Trac:
Milestone: Tor: 0.2.??? to Tor: 0.3.???

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

Trac:
Milestone: Tor: 0.3.??? to Tor: unspecified
Keywords: N/A deleted, tor-03-unspecified-201612 added

Remove an old triaging keyword.

Trac:
Keywords: tor-03-unspecified-201612 deleted, N/A added

Turns out that tor-auth is for directory authority so make it clearer with tor-dirauth

Trac:
Keywords: tor-auth deleted, tor-dirauth added

We still know we need to analyze old-consensus usage, but we have other tickets for that. Closing this one.

Trac:
Sponsor: N/A to N/A
Status: new to closed
Resolution: N/A to not a bug
Severity: N/A to Normal
Reviewer: N/A to N/A

closed

moved to tpo/core/tor#4872 (closed)