Dirauths should expose the value of `MinUptimeHidServDirectoryV2` as a vote flag-threshold

I think it's important that MinUptimeHidServDirectoryV2 is a public value for each directory authority, so that we can monitor which authorities have switched to the newest value (it used to be 26 hours, now it's 96 afaik).

I suggest that this gets exposed in the flag-thresholds line of the vote documents. If other people think this is reasonable, it will require an easy torspec patch and a tor patch.

changed milestone to %Tor: unspecified

added component::core tor/tor milestone::Tor: unspecified points::0.5 priority::medium prop224 severity::normal sponsor::R-can status::new tor-dirauth tor-hs type::enhancement labels

flag-thresholds seems to contain similar info for the other flags.

Good idea!

flag-thresholds makes more sense here, I think. That line is only occurs in votes, not in the consensus. In contrast to that, params is something that directory authorities vote on and that gets included in the consensus, which is not what we want here.

I suggest a new performance threshold like this: hsdir-uptime -- Uptime (in hours) required for a relay to be marked as HSDir.

It would be better to leave adversaries guessing about their sybils.

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

Trac:
Status: new to assigned

Marking triaged-out items from first round of 0.2.7 triage.

Trac:
Keywords: N/A deleted, 027-triaged-1-out added

Make all non-needs_review, non-needs_revision, 027-triaged-1-out items belong to 0.2.???

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

Milestone renamed

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

Trac:
Keywords: tor-dirauth, 027-triaged-1-out deleted, N/A added
Reviewer: N/A to N/A
Severity: N/A to Normal
Sponsor: N/A to SponsorR-can
Type: defect to enhancement

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

Change the status of all assigned/accepted Tor tickets with owner="" to "new".

Trac:
Status: assigned to new

I agree and especially with the prop224 work, that "v2" naming is not appropriate. However, they will differ I believe because prop224 could have a lower threshold for becoming an HSDir.

Trac:
Points: N/A to 0.5
Parent: N/A to #12424 (moved)
Keywords: N/A deleted, tor-dirauth, prop224 added

Not much to do with prop224...

Trac:
Parent: #12424 (moved) to N/A

Trac:
Summary: Dirauths should expose the value of MinUptimeHidServDirectoryV2 as a vote/consensus parameter to Dirauths should expose the value of MinUptimeHidServDirectoryV2 as a vote flag-threshold

(modified ticket body to pick the flag-thresholds line, not the param line.)

Trac:
Description: I think it's important that MinUptimeHidServDirectoryV2 is a public value for each directory authority, so that we can monitor which authorities have switched to the newest value (it used to be 26 hours, now it's 96 afaik).

I suggest that this gets exposed in the flag-thresholds or params line of the vote documents. If other people think this is reasonable, it will require an easy torspec patch and a tor patch.

to

I think it's important that MinUptimeHidServDirectoryV2 is a public value for each directory authority, so that we can monitor which authorities have switched to the newest value (it used to be 26 hours, now it's 96 afaik).

I suggest that this gets exposed in the flag-thresholds line of the vote documents. If other people think this is reasonable, it will require an easy torspec patch and a tor patch.

changed time estimate to 4h

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