Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 316
    • Issues 316
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 34
    • Merge requests 34
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #372
Closed
Open
Created Jan 04, 2007 by Roger Dingledine@armaReporter

Caches collect old network statuses?

I found http://freehaven.net/~arma/all on http://62.48.34.110/tor/status/all

it came from tortuga. Notice how some of the network statuses are from like 6 months ago. And notice how they're from various test internal networks also.

I noticed it because my Tor client chose this cache to ask for its statuses.

So I picked a random directory cache and asked it for its statuses: http://212.112.242.159/tor/status/all and it has all these extra statuses too!

So:

A) Why aren't they discarding them after 10 days? They can't all have totally broken clocks.

B) By what process are these network statuses making their way into the community caches?

C) Do we want to be pickier about what we cache, e.g. some of our trusted authorities need to think it's an authority?

[Automatically added by flyspray2trac: Operating System: All]

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking