Opened 14 years ago

Last modified 7 years ago

#236 closed defect (Implemented)

cache network status of unknown authorities

Reported by: weasel Owned by:
Priority: Low Milestone: 0.1.1.11-alpha
Component: Core Tor/Tor Version: 0.1.1.10-alpha
Severity: Keywords:
Cc: weasel Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

<nickm> arma: We should think about what will happen when we add new

directories.

<nickm> directory authorities, that is.
<arma2> you mean anonymity attacks?
<nickm> Well, that too.
<nickm> But I meant in terms of everything working.
<nickm> I looked over the code, and I see that it's only an info (not a warn)

to be given a network-status you don't recognize: that's good, since
caches will ask authorities for "everybody!", and older ones will get
authorities they won't recognize.

<nickm> OTOH, would it be a good idea to cache (if not use!) network-status

docs from unrecognized authorities?

<nickm> that way directory caches don't become less useful when we add new dir

authorities.

<arma2> yes, i guess that would be useful to cache them.
<arma2> tho we want to not cache too many.
<nickm> right.
<arma2> and we want to not use them (right?)
<nickm> and again, right.
<arma2> that should get fixed for 0.1.1.11-alpha if we are smart
<nickm> I say cap it at 16 unrecognized authority identities.
<arma2> is it easy to fix?
<nickm> dunno
<arma2> ok.
<nickm> let me check.

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (2)

comment:1 Changed 14 years ago by nickm

flyspray2trac: bug closed.
Implemented in CVS.

comment:2 Changed 7 years ago by nickm

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