Don't vote HSDir if we aren't voting Fast

Right now when you spin up a new relay, it gets the HSDir flag before it gets measured. So for the sybil attackers that are aiming to mess with hidden service descriptors in some way, we have to notice them faster than we have to notice other sybils. This is no fun, and easy to fix with very few downsides.

changed milestone to %Tor: 0.2.7.x-final in legacy/trac

added 026-backport in Legacy / Trac component::core tor/tor in Legacy / Trac milestone::Tor: 0.2.7.x-final in Legacy / Trac owner::dgoulet in Legacy / Trac parent::16538 in Legacy / Trac priority::medium in Legacy / Trac resolution::implemented in Legacy / Trac sponsor::R in Legacy / Trac status::closed in Legacy / Trac type::enhancement in Legacy / Trac labels

(Excitingly, I don't think I'll get my desired behavior here until legacy/trac#12877 (moved) is resolved too.)

Requiring Fast will make HSDir performance more reliable, and raise the bar for the amount of bandwidth sybils will need to dedicate to each instance to get HSDir. This will be at the cost of fewer relays with HSDir, which may even be a good thing.

Trac:
Keywords: N/A deleted, 026-backport added
Parent: N/A to legacy/trac#8243 (moved)

I've removed the Parent ID so we can close the ticket because it has been merged.

This is still linked to legacy/trac#8243 (moved) in a way that it's an ongoing effort on making relay with HSDir flag be reliable.

Trac:
Parent: legacy/trac#8243 (moved) to N/A

Trac:
Parent: N/A to legacy/trac#16538 (moved)

Trac:
Keywords: N/A deleted, TorCore201508 added
Status: new to accepted
Owner: N/A to dgoulet

I'd merge patches for these for 0.2.7 if they come in on time. In some cases, that will require figuring out an as-yet-unsolved bugs.

Trac:
Keywords: N/A deleted, PostFreeze027 added

See branch: bug15963_026_01. This applies on 0.2.6 for backport and 0.2.7.

Here are some extra considerations. We currently have 2745 HSDirs and with this extra requirement, we'll be going down to 2342 HSDirs. Not too drastic.

Trac:
Status: accepted to needs_review

Merged to master; marking for possible backport.

Trac:
Milestone: Tor: 0.2.7.x-final to Tor: 0.2.6.x-final

Trac:
Status: needs_review to accepted
Keywords: PostFreeze027, TorCore201508, tor-auth deleted, N/A added

Bulk-replace SponsorR keyword with SponsorR sponsor field in Tor component.

Trac:
Sponsor: N/A to SponsorR
Keywords: SponsorR deleted, N/A added

It's a feature! Not backporting.

Trac:
Resolution: N/A to implemented
Status: accepted to closed
Milestone: Tor: 0.2.6.x-final to Tor: 0.2.7.x-final

closed

mentioned in issue legacy/trac#16524 (moved)

moved from legacy/trac#15963 (moved)

added Feature label and removed 1 deleted label

removed 1 deleted label