Opened 3 years ago

Closed 2 years ago

#18140 closed defect (implemented)

Update dir-spec for "reasonably live" consensuses

Reported by: teor Owned by: nickm
Priority: Low Milestone: Tor: 0.3.2.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-spec, doc
Cc: Actual Points:
Parent ID: Points: .1
Reviewer: Sponsor:

Description

In networkstatus_get_reasonably_live_consensus() and check_expired_networkstatus_callback(), tor has the concept of a "reasonably live" consensus. A consensus is reasonably live if it expired less than 24 hours ago.

This isn't in the directory spec, should it be?

Child Tickets

Change History (11)

comment:1 Changed 3 years ago by nickm

Priority: MediumLow

comment:2 Changed 3 years ago by nickm

Milestone: Tor: 0.2.8.x-finalTor: 0.2.9.x-final

Throw most 0.2.8 "NEW" tickets into 0.2.9. I expect that many of them will subsequently get triaged out.

comment:3 Changed 3 years ago by nickm

Points: very small

comment:4 Changed 3 years ago by nickm

Points: very small.1

comment:5 Changed 3 years ago by isabela

Keywords: isaremoved added
Milestone: Tor: 0.2.9.x-finalTor: 0.2.???

comment:6 Changed 3 years ago by teor

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

Milestone renamed

comment:7 Changed 3 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:8 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:9 Changed 2 years ago by nickm

Keywords: isaremoved removed

comment:10 Changed 2 years ago by nickm

Milestone: Tor: unspecifiedTor: 0.3.2.x-final
Owner: set to nickm
Status: newaccepted

comment:11 Changed 2 years ago by nickm

Resolution: implemented
Status: acceptedclosed

Done in 85d7c57bbdf549.

Note: See TracTickets for help on using tickets.