Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
T
Tor
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,067
    • Issues 1,067
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 19
    • Merge Requests 19
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • The Tor Project
  • Core
  • Tor
  • Issues
  • #22473

Closed
Open
Opened Jun 02, 2017 by Roger Dingledine@armaReporter

Do any controllers still use getinfo network-status?

Tor long ago had a "getinfo network-status" where it would cobble together a v1 "running-routers" style directory status for the controller. It's been deprecated in control-spec since 2007, and in 0.3.1.1-alpha (legacy/trac#21703 (moved)) we made Tor issue a warning log message when you use it.

It has some weird side effects when you ask a directory authority for getinfo network-status, since it makes the dir auth recompute whether it thinks relays are running.

Do any controllers still use it? I cc a developer from arm, txtorcon, and tor launcher, and if they all say "no, what is that", I say we take it out in Tor 0.3.2.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.4.5.x-stable
Milestone
Tor: 0.4.5.x-stable (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: tpo/core/tor#22473