Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 832
    • Issues 832
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 31
    • Merge requests 31
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #2411

Closed
Open
Created Jan 18, 2011 by Roger Dingledine@armaReporter

expand getinfo circuit-status to show build_state flags

We've got a usability bug where users are misinterpreting the circuit listing on Vidalia's network map. In legacy/trac#2114 (closed) I suggest that Vidalia should start giving the user more information.

But Tor really doesn't export enough information for Vidalia to know what to say. Right now we export a PURPOSE= argument, but the string we send isn't very useful. Also, we don't export some flags, like onehup_tunnel, which Vidalia needs to know to tell the user that the circuit in question is probably for fetching directory information.

We should come up with a spec change and implement it. Shouldn't be too hard.

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