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

Closed (moved)
Open
Opened Nov 13, 2017 by Roger Dingledine@arma

Add a new "outdated" field to distinguish between outdated and too new tor versions

https://atlas.torproject.org/#search/moria1 shows this text at the top: "This relay is running an outdated Tor version and should be updated to a recent release of Tor that may contain important fixes."

But the relay is running "Tor 0.3.3.0-alpha-dev". This is not an outdated Tor version -- it is newer than any of the recommended versions.

Tor has some somewhat complicated logic for deciding whether a version is obsolete -- see tor_version_is_obsolete(). Is atlas's best plan to try to reproduce Tor's logic? Should we try to specify it, e.g. in version-spec.txt, so external programs have a chance of getting it right?

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