Relays can upload a new descriptor every 2 minutes

Two relays started publishing descriptors every 2 minutes, and this caused issues for Metrics-lib: https://lists.torproject.org/pipermail/metrics-team/2018-February/000661.html

Maybe it's a crashing bug in 0.3.3.1-alpha?

In any case, we should probably restrict relays to a few (~6?) descriptors per hour consensus interval, and enforce this limit using the state file.

changed milestone to %Tor: unspecified

added 033-included-20180320 033-triage-20180320 033-unreached-backport 034-removed-must-2018-09-05 035-removed-20180711 component::core tor/tor crash? milestone::Tor: unspecified points::1 priority::medium regression? severity::normal status::new tor-dos-related? type::defect version::tor 0.3.3.1-alpha labels

In test networks, we should use the consensus interval, and not hard-code one hour.

Trac:
Description: Two relays started publishing descriptors every 2 minutes, and this caused issues for Metrics-lib: https://lists.torproject.org/pipermail/metrics-team/2018-February/000661.html

Maybe it's a crashing bug in 0.3.3.1-alpha?

In any case, we should probably restrict relays to a few (~6?) descriptors per hour, and enforce this limit using the state file.

to

Two relays started publishing descriptors every 2 minutes, and this caused issues for Metrics-lib: https://lists.torproject.org/pipermail/metrics-team/2018-February/000661.html

Maybe it's a crashing bug in 0.3.3.1-alpha?

In any case, we should probably restrict relays to a few (~6?) descriptors per hour consensus interval, and enforce this limit using the state file.

Mark some tickets as possibly belonging in 033-must.

Trac:
Keywords: tor-dos-related? crash? deleted, 033-maybe-must, crash?, tor-dos-related? added

move 033-maybe-must into 033-must

Trac:
Keywords: 033-maybe-must deleted, 033-must added

Assigning some 033-must tickets to myself.

Trac:
Owner: N/A to isis
Status: new to accepted

Trac:
Keywords: N/A deleted, regression? added

Marking all tickets reached by current round of 033 triage.

Trac:
Keywords: N/A deleted, 033-triage-20180320 added

Mark 033-must tickets as triaged-in for 0.3.3

Trac:
Keywords: N/A deleted, 033-included-20180320 added

Possibly related (and with more hints if so): #25686 (moved).

Should we count descriptor uploads in the dirauth state files, or locally on the OR? (I'm inclined to the former so it's not circumventable/gameable.)

arma mentioned that we shouldn't write anything to disk, but simply have dirauth-side rate limits. (I assume we already have functionality for rate-limiting somewhere, but I've never touched that code, so if someone who knows more about it wouldn't mind pointing me in the right direction, that'd be awesome!)

Deferring to 0.3.4. Rate-limiting may not be the right answer (Roger says), and suggests that we try to fix the underlying bug instead (#25686 (moved)?)

Trac:
Milestone: Tor: 0.3.3.x-final to Tor: 0.3.4.x-final
Keywords: 033-must, 033-included-20180320 deleted, 033-included-20180320 033-backport, 034-must added

Removing myself as owner for now, since I was the owner as part of "everyone take a few 033-must tickets".

Trac:
Status: accepted to assigned
Owner: isis to N/A

no progress during 0.3.4

Trac:
Milestone: Tor: 0.3.4.x-final to Tor: 0.3.5.x-final

These tickets are being triaged out of 0.3.5. The ones marked "035-roadmap-proposed" may return.

Trac:
Milestone: Tor: 0.3.5.x-final to Tor: unspecified
Keywords: 033-included-20180320 033-backport deleted, 035-removed-20180711, 033-backport, 033-included-20180320 added

Make everything that is assigned to no-one new again.

Trac:
Status: assigned to new

These tickets were removed from 0.3.4, so they can't be 034-must.

Trac:
Keywords: 034-must deleted, 034-removed-must-2018-09-05 added

These open, non-merge_ready tickets can not get backported to 0.3.3, because 0.3.3 is now unsupported.

Trac:
Keywords: 033-backport deleted, N/A added

Hmm, I guess they should still get 033-backport-unreached

Trac:
Keywords: N/A deleted, 033-backport-unreached added

Fix 033-unreached-backport spelling.

Trac:
Keywords: 033-backport-unreached deleted, 033-unreached-backport added

changed time estimate to 8h

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