Opened 3 years ago

Last modified 23 months ago

#20601 new enhancement

Clients should reject outdated consensuses as soon as they parse them

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: easy, tor-client timestamp consensus download
Cc: Actual Points:
Parent ID: Points: 0.5
Reviewer: Sponsor:

Description

We should check when we reject outdated consensuses, and consider doing it sooner.

Split off #20511, defends against bugs similar to #20499.

Child Tickets

Change History (5)

comment:1 Changed 2 years ago by teor

When delivering a consensus over the control port, Tor will provide the cached consensus, no matter how old it is. This is a problem when combined with #20667, which stops clients downloading a full consensus in 0.3.0.

It affects at least the bandwidth authorities (#20621), and probably every other client that expects FetchUselessDescriptors to deliver a full consensus.

comment:2 Changed 2 years ago by nickm

Type: defectenhancement

batch modify: I think these are "enhancement", though I could be wrong about some.

comment:3 Changed 2 years ago by nickm

Keywords: triaged-out-20160116 added
Milestone: Tor: 0.3.0.x-finalTor: unspecified

comment:4 Changed 2 years ago by nickm

Keywords: triaged-out-20170116 added; triaged-out-20160116 removed

comment:5 Changed 23 months ago by nickm

Keywords: tor-client timestamp consensus download added; triaged-out-20170116 removed
Note: See TracTickets for help on using tickets.