Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T torflow
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Network Health
  • torflow
  • Issues
  • #7025
Closed
Open
Issue created Oct 03, 2012 by Mike Perry@mikeperryOwner

Support Tor 0.2.3.x control port event keyword reordering

Right now, the bandwidth auths are not going to work with Tor 0.2.3.x because for some reason we needed to deliberately break the control-spec.txt by reordering keywords... legacy/trac#3679 (moved) attempted to fix this by rewriting all of our event parsing, but that caused strange issues with the bw auths.

We should just try to update the regex instead, as a simpler change.

Assignee
Assign to
Time tracking