diff options
| author | George Kadianakis <desnacked@riseup.net> | 2017-01-17 12:59:41 +0200 |
|---|---|---|
| committer | George Kadianakis <desnacked@riseup.net> | 2017-01-17 14:35:38 +0200 |
| commit | 2938fd3b859a71b9f484623b8dae61e8e7a7f7ec (patch) | |
| tree | 427fe5664a9eb5d195326182ee2d818d7db8834a /changes/bug21052 | |
| parent | 111c66b2f0f58206026ca6a72852c3afcb56b9e7 (diff) | |
| download | tor-2938fd3b859a71b9f484623b8dae61e8e7a7f7ec.tar.gz tor-2938fd3b859a71b9f484623b8dae61e8e7a7f7ec.zip | |
prop271: When we exhaust all guards, mark all of them for retry.
In the past, when we exhausted all guards in our sampled set, we just
waited there till we mark a guard for retry again (usually takes 10 mins
for a primary guard, 1 hour for a non-primary guard). This patch marks
all guards as maybe-reachable when we exhaust all guards (this can
happen when network is down for some time).
Diffstat (limited to 'changes/bug21052')
| -rw-r--r-- | changes/bug21052 | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/changes/bug21052 b/changes/bug21052 new file mode 100644 index 0000000000..0597b3b306 --- /dev/null +++ b/changes/bug21052 @@ -0,0 +1,4 @@ + o Minor bugfixes (client, guards): + - Fix a bug of the new guard algorithm where tor could stall for up to 10 + minutes before retrying a guard after a long period of no network. + Fixes bug 21052; bugfix on 0.3.0.1-alpha. |