Opened 12 years ago

Last modified 7 years ago

#372 closed defect (Fixed)

Caches collect old network statuses?

Reported by: arma Owned by:
Priority: High Milestone:
Component: Core Tor/Tor Version: 0.1.1.26
Severity: Keywords:
Cc: arma Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

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]

Child Tickets

Change History (5)

comment:1 Changed 12 years ago by nickm

A) is a bug, and should get fixed in 0.1.2.6.

B) I don't know.

C) No; in the future, we want to move to a voting scheme, and for now, the behavior of
caching statuses from authorities we don't recognize is as designed. (Not discarding
them _is_ a bug, tho.)

comment:2 Changed 12 years ago by nickm

(A) is fixed as of r9324.

comment:3 Changed 12 years ago by nickm

For (B), all I can figure is that some caches have (or once had) additional DirServers configured.
I'm going to B closed, unless it turns out that we're caching network statuses given to us by somebody
we didn't believe in as a dirserver.

comment:4 Changed 12 years ago by nickm

flyspray2trac: bug closed.

comment:5 Changed 7 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.