Opened 22 months ago

Last modified 17 months ago

#24238 new defect

Bug: Generated a networkstatus vote we couldn't parse because of invalid consensus param

Reported by: Sebastian Owned by:
Priority: Very Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: 033-triage-20180320, 033-removed-20180320
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I accidentally put "MinUptimeHidServDirectoryV2 96 hours" into my consensus params instead of making it its own line in the torrc. Tor had no problem with this during startup, but then tried to create a vote that had a params line starting with a 96, which it then choked on during parsing. The right fix is probably along the lines of stricter ConsensusParams validation i think.

Child Tickets

Change History (3)

comment:1 Changed 17 months ago by nickm

Keywords: 033-triage-20180320 added

Marking all tickets reached by current round of 033 triage.

comment:2 Changed 17 months ago by nickm

Keywords: 033-removed-20180320 added

Mark all not-already-included tickets as pending review for removal from 0.3.3 milestone.

comment:3 Changed 17 months ago by nickm

Milestone: Tor: 0.3.3.x-finalTor: unspecified

These tickets were marked as removed, and nobody has said that they can fix them. Let's remember to look at 033-removed-20180320 as we re-evaluate our triage process, to see whether we're triaging out unnecessarily, and to evaluate whether we're deferring anything unnecessarily. But for now, we can't do these: we need to fix the 033-must stuff now.

Note: See TracTickets for help on using tickets.