clients fail to update guard selection
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]