Opened 4 years ago

Last modified 16 months ago

#14150 new enhancement

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

Reported by: asn Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-hs, prop224, tor-dirauth
Cc: Actual Points:
Parent ID: Points: 0.5
Reviewer: Sponsor: SponsorR-can

Description (last modified by arma)

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.

Child Tickets

Change History (16)

comment:1 Changed 4 years ago by teor

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

comment:2 Changed 4 years ago by karsten

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.

comment:3 Changed 4 years ago by cypherpunks

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

comment:4 Changed 4 years ago by nickm

Milestone: Tor: 0.2.6.x-finalTor: 0.2.7.x-final

comment:5 Changed 4 years ago by nickm

Status: newassigned

comment:6 Changed 4 years ago by nickm

Keywords: 027-triaged-1-out added

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

comment:7 Changed 4 years ago by nickm

Milestone: Tor: 0.2.7.x-finalTor: 0.2.???

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

comment:8 Changed 2 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:9 Changed 2 years ago by dgoulet

Keywords: tor-dirauth 027-triaged-1-out removed
Severity: Normal
Sponsor: SponsorR-can
Type: defectenhancement

comment:10 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

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

comment:11 Changed 19 months ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:12 Changed 19 months ago by nickm

Status: assignednew

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

comment:13 Changed 19 months ago by dgoulet

Keywords: prop224 tor-dirauth added
Parent ID: #12424
Points: 0.5

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.

comment:14 Changed 16 months ago by dgoulet

Parent ID: #12424

Not much to do with prop224...

comment:15 Changed 16 months ago by arma

Summary: Dirauths should expose the value of `MinUptimeHidServDirectoryV2` as a vote/consensus parameterDirauths should expose the value of `MinUptimeHidServDirectoryV2` as a vote flag-threshold

comment:16 Changed 16 months ago by arma

Description: modified (diff)

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

Note: See TracTickets for help on using tickets.