Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

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.

  • Legacy
  • TracTrac
  • Issues
  • #28676

Closed (moved)
Open
Opened Dec 01, 2018 by Trac@tracbot

Tor versions of Tor nodes should be accessible through ControlPort

If extra torrc options (such as FetchUselessDescriptors) are not used, Tor's ControlPort commands GETINFO ns/id/FINGERPINT and GETINFO ns/name/nickname do not print Tor versions of the corresponding nodes. Their versions still can be read from a file /var/lib/tor/cached-microdesc-consensus (lines v Tor x.x.x.x) directly, but I cannot see any reason why applications cannot learn them from ControlPort too. Also, I didn't find other ControlPort commands which print these Tor versions.

This problem [disccused] in relation to Nyx:

Inverse situation is with Tor version: it is shown in /var/lib/tor/cached-microdesc-consensus but Nyx does not show it in information about relays (connections window). Can relay's Tor version be learned from ControlPort too?

Trac:
Username: wagon

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#28676