diff options
| author | Roger Dingledine <arma@torproject.org> | 2016-10-01 16:34:17 -0400 |
|---|---|---|
| committer | Roger Dingledine <arma@torproject.org> | 2016-10-01 16:34:17 -0400 |
| commit | bfaded9143d127cb32407a7a58159383fa9ed333 (patch) | |
| tree | 1cfe84789182294f7a5c49495e36733197771ae5 /changes/bug20269 | |
| parent | 53255e925c474f9d5cb30c1de4da025e6d709e9a (diff) | |
| download | tor-bfaded9143d127cb32407a7a58159383fa9ed333.tar.gz tor-bfaded9143d127cb32407a7a58159383fa9ed333.zip | |
Bridge-using clients now use their cached microdesc consensus
Clients that use bridges were ignoring their cached microdesc-flavor
consensus files, because they only thought they should use the microdesc
flavor once they had a known-working bridge that could offer microdescs,
and at first boot no bridges are known-working.
This bug caused bridge-using clients to download a new microdesc consensus
on each startup.
Fixes bug 20269; bugfix on 0.2.3.12-alpha.
Diffstat (limited to 'changes/bug20269')
| -rw-r--r-- | changes/bug20269 | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/changes/bug20269 b/changes/bug20269 new file mode 100644 index 0000000000..5d580bf3cc --- /dev/null +++ b/changes/bug20269 @@ -0,0 +1,4 @@ + o Minor bugfixes: + - When clients that use bridges start up with a cached consensus + on disk, they were ignoring it and downloading a new one. Now they + use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha. |