Opened 23 months ago

Last modified 19 months ago

#22473 new defect

Do any controllers still use getinfo network-status?

Reported by: arma Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: 032-unreached
Cc: atagar, meejah, mcs, brade Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

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) 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.

Child Tickets

Change History (3)

comment:1 Changed 23 months ago by mcs

Cc: brade added

Tor Launcher does not use this command (and never has, I am 99% sure).

comment:2 Changed 23 months ago by meejah

txtorcon does not.

It uses GETINFO ns/all to set up its notion of Tor's notion of the current relays.

comment:3 Changed 19 months ago by nickm

Keywords: 032-unreached added
Milestone: Tor: 0.3.2.x-finalTor: unspecified

Mark a large number of tickets that I do not think we will do for 0.3.2.

Note: See TracTickets for help on using tickets.