From 4c297f74f79e0e3d357d20bfc584eccc758d1fd8 Mon Sep 17 00:00:00 2001 From: Roger Dingledine Date: Mon, 31 Aug 2009 16:14:41 -0400 Subject: Only send reachability status events on overall success/failure We were telling the controller about CHECKING_REACHABILITY and REACHABILITY_FAILED status events whenever we launch a testing circuit or notice that one has failed. Instead, only tell the controller when we want to inform the user of overall success or overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported by SwissTorExit. --- ChangeLog | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'ChangeLog') diff --git a/ChangeLog b/ChangeLog index 34ba6a7168..806d147d99 100644 --- a/ChangeLog +++ b/ChangeLog @@ -23,6 +23,12 @@ Changes in version 0.2.1.20 - 2009-??-?? 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. + - We were telling the controller about CHECKING_REACHABILITY and + REACHABILITY_FAILED status events whenever we launch a testing + circuit or notice that one has failed. Instead, only tell the + controller when we want to inform the user of overall success or + overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported + by SwissTorExit. Changes in version 0.2.1.19 - 2009-07-28 -- cgit v1.2.3-54-g00ecf