Opened 13 years ago

Last modified 7 years ago

#287 closed defect (Fixed)

clients fail to update guard selection

Reported by: goodell Owned by:
Priority: Low Milestone: 0.1.2.x-final
Component: Core Tor/Tor Version: 0.1.1.18-rc
Severity: Keywords:
Cc: goodell Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

With version 0.1.1.18-rc, Tor sometimes continues to select a particular Tor
server as an entry node, even when all of the authorities believe that it is
unsuited for use as a guard. This situation persists for days, possibly
indefinitely.

Perhaps the server in question was suitable as a guard at one time, but Tor
must rebalance the guard list not only upon startup but also whenever
authorities change the listing status of potential guard candidates.

Tor clients MUST continually ensure that the guard selection matches the
candidacy indication provided by the authorities. Otherwise, the clients are
again shackled with unsuitable guards -- a phenomenon that we seek to avoid
with the stringent guard requirements.

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (2)

comment:1 Changed 13 years ago by nickm

flyspray2trac: bug closed.
Fixed in r8519. Fix will appear in 0.1.2.2-alpha.

Clients are no longer "shackled". I suppose this means we've struck off the chains of their oppressors or something.

comment:2 Changed 7 years ago by nickm

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