aboutsummaryrefslogtreecommitdiff
path: root/ChangeLog
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2007-08-18 18:20:42 +0000
committerNick Mathewson <nickm@torproject.org>2007-08-18 18:20:42 +0000
commit676d8622deb70e5d14b19bb22d0f0856cfaad9b3 (patch)
tree95391b4561e22a1ec9622e53d330653df91b96f5 /ChangeLog
parent648c8261fd8101ef43de57e80a41c67a96ec5330 (diff)
downloadtor-676d8622deb70e5d14b19bb22d0f0856cfaad9b3.tar
tor-676d8622deb70e5d14b19bb22d0f0856cfaad9b3.tar.gz
r14659@catbus: nickm | 2007-08-18 14:19:34 -0400
When we are loading state info from disk, never believe any date in the future. Doing so can keep us from retrying guards, rotating onion keys, storing bandwidth info, etc. Fixes bug 434, and others. Backport candidate, once it has been tested. svn:r11166
Diffstat (limited to 'ChangeLog')
-rw-r--r--ChangeLog7
1 files changed, 7 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog
index 470b3379b..bcfece2b6 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -46,6 +46,13 @@ Changes in version 0.2.0.5-alpha - 2007-??-??
every time we change any piece of our config.
- Fix a bug with AutomapHostsOnResolve that would always cause the second
request to fail. Bug reported by Kate. Bugfix on 0.2.0.3-alpha.
+ - When loading bandwidth history, do not believe any information in
+ the future. Fixes bug 434.
+ - When loading entry guard information, do not believe any information
+ in the future.
+ - When we have our clock set far in the future and generate an onion key,
+ then re-set our clock to be correct, we should not stop the onion
+ key from getting rotated.
Changes in version 0.2.0.4-alpha - 2007-08-01