diff options
| author | Roger Dingledine <arma@torproject.org> | 2009-08-28 03:42:09 -0400 |
|---|---|---|
| committer | Roger Dingledine <arma@torproject.org> | 2009-08-28 03:42:09 -0400 |
| commit | 64f393d56f8ff58223db56f3b8e64f0074877616 (patch) | |
| tree | 0849d2d72e12be11036892c038f06000c790aed4 /ChangeLog | |
| parent | d52284559b7e06521cff2c7e8f3c710922b73dc6 (diff) | |
| download | tor-64f393d56f8ff58223db56f3b8e64f0074877616.tar.gz tor-64f393d56f8ff58223db56f3b8e64f0074877616.zip | |
Only send netinfo clock_skew to controller if an authority told us so
We were triggering a CLOCK_SKEW controller status event whenever
we connect via the v2 connection protocol to any relay that has
a wrong clock. Instead, we should only inform the controller when
it's a trusted authority that claims our clock is wrong. Bugfix
on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
Diffstat (limited to 'ChangeLog')
| -rw-r--r-- | ChangeLog | 5 |
1 files changed, 5 insertions, 0 deletions
@@ -18,6 +18,11 @@ Changes in version 0.2.1.20 - 2009-??-?? - Fix an extremely rare infinite recursion bug that could occur if we tried to log a message after shutting down the log subsystem. Found by Matt Edman. Bugfix on 0.2.0.16-alpha. + - We were triggering a CLOCK_SKEW controller status event whenever + we connect via the v2 connection protocol to any relay that has + a wrong clock. Instead, we should only inform the controller when + it's a trusted authority that claims our clock is wrong. Bugfix + on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit. Changes in version 0.2.1.19 - 2009-07-28 |