[tor-bugs] #28676 [Core Tor/Tor]: Tor versions of Tor nodes should be accessible through ControlPort

Tor Bug Tracker & Wiki blackhole at torproject.org
Fri Dec 21 08:07:36 UTC 2018


#28676: Tor versions of Tor nodes should be accessible through ControlPort
--------------------------+----------------------------------
 Reporter:  wagon         |          Owner:  (none)
     Type:  enhancement   |         Status:  new
 Priority:  Medium        |      Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |        Version:  Tor: 0.3.4.9
 Severity:  Normal        |     Resolution:
 Keywords:                |  Actual Points:
Parent ID:  #7646         |         Points:
 Reviewer:                |        Sponsor:
--------------------------+----------------------------------

Comment (by wagon):

 Replying to [comment:19 teor]:
 > Replying to [comment:18 wagon]:
 > > There is a command `GETINFO dir/status-vote/current/consensus` which
 returns the same output as the content of the file `cached-microdesc-
 consensus`. So, it has Tor versions of all nodes. However, output of this
 command is very big, so tools which use `ControlPort` may not behave
 nicely if this command is run often.
 > >
 > > This command works even if `UseMicrodescriptors` is set to 0.
 >
 > This command gets the full (ns) consensus from disk, so it *only* works
 if one of the following conditions is true:
 > * `UseMicrodescriptors` is set to 0, or
 > * the Tor instance is a directory cache, or
 > * the Tor instance is a directory authority, or
 > * the Tor instance is using a data directory that previously downloaded
 a full consensus. This full consensus may be outdated.
 I'm not testing it on relay, so only the first and the last options are
 possible. Indeed, `UseMicrodescriptors` is set to 0, and Tor instance has
 "previously downloaded full consensus", but your explanation doesn't not
 look correct. I compared the output of the command `GETINFO dir/status-
 vote/current/consensus` with the content of the file `cached-microdesc-
 consensus`. They are not only different, the even have a clear sign of
 this difference: I added `UseMicrodescriptors 0` few days back, when
 `0.3.5.6-rc` wans't released yet, so the file `cached-microdesc-consensus`
 still knows nothing about this new version, while GETINFO command knows it
 and lists it. Thus, I say my initial point  still holds:
 1. Tor knows this consensus.
 2. Tor doesn't store it on the disk and donesn't update the file `cached-
 microdesc-consensus`.
 3. When `GETINFO dir/status-vote/current/consensus` is requested, tor
 doesn't read the content of the output from the disk.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28676#comment:22>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the tor-bugs mailing list