summaryrefslogtreecommitdiff
path: root/ChangeLog
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2007-10-30 15:17:07 +0000
committerNick Mathewson <nickm@torproject.org>2007-10-30 15:17:07 +0000
commitc0c2001a5b8fd3907c7ba93eccbd536786f57594 (patch)
treec7aa35ecb0eab620cbd592451600347410da4dee /ChangeLog
parent7709fb7143cc272c04f9de3970e4ac0fe3a000d6 (diff)
downloadtor-c0c2001a5b8fd3907c7ba93eccbd536786f57594.tar.gz
tor-c0c2001a5b8fd3907c7ba93eccbd536786f57594.zip
r16279@catbus: nickm | 2007-10-30 11:14:29 -0400
Improved skew reporting: "You are 365 days in the duture" is more useful than "You are 525600 minutes in the future". Also, when we get something that proves we are at least an hour in the past, tell the controller "CLOCK_SKEW MIN_SKEW=-3600" rather than just "CLOCK_SKEW" svn:r12283
Diffstat (limited to 'ChangeLog')
-rw-r--r--ChangeLog6
1 files changed, 6 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog
index 1a70f16b75..590ffc329b 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -37,6 +37,12 @@ Changes in version 0.2.0.10-alpha - 2007-1?-??
to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
we start knowing some directory caches.
- When we receive a consensus from the future, warn about skew.
+ - Improve skew reporting: try to give the user a better log message about
+ how skewed they are, and how much this matters.
+
+ o Minor features (controller):
+ - When reporting clock skew, and we only have a lower bound on the amount
+ of skew, amount anyway, marked as a lower bound.
- Utilities:
- Update linux-tor-prio.sh script to allow QoS based on the uid of