Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #24238

Closed (moved)
(moved)
Open
Created Nov 11, 2017 by Sebastian Hahn@sebastian

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

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.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking