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
  • #22473

Closed (moved)
(moved)
Open
Created Jun 02, 2017 by Roger Dingledine@arma

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 (#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
Time tracking