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

Closed (moved)
(moved)
Open
Created 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 an admin enable hashed storage. More information
Assignee
Assign to
Time tracking