summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2009-08-28 03:47:18 -0400
committerRoger Dingledine <arma@torproject.org>2009-08-28 03:47:18 -0400
commit0bb59f1c38eef467a353faf1a30cf93b64209a27 (patch)
tree2c2a749c0b3284e023c2a14afbff7756f5f8ef5a /doc
parent85e22a8adb8c4f833498d8ad824c3ed61ee61acb (diff)
parent64f393d56f8ff58223db56f3b8e64f0074877616 (diff)
downloadtor-0bb59f1c38eef467a353faf1a30cf93b64209a27.tar.gz
tor-0bb59f1c38eef467a353faf1a30cf93b64209a27.zip
Merge branch 'maint-0.2.1'
Diffstat (limited to 'doc')
-rw-r--r--doc/spec/control-spec.txt22
1 files changed, 14 insertions, 8 deletions
diff --git a/doc/spec/control-spec.txt b/doc/spec/control-spec.txt
index fc4242ea16..1e3246e848 100644
--- a/doc/spec/control-spec.txt
+++ b/doc/spec/control-spec.txt
@@ -1254,20 +1254,26 @@
CLOCK_SKEW
SKEW="+" / "-" SECONDS
MIN_SKEW="+" / "-" SECONDS.
- SOURCE="DIRSERV:IP:Port" / "NETWORKSTATUS:IP:PORT" / "CONSENSUS"
+ SOURCE="DIRSERV:" IP ":" Port /
+ "NETWORKSTATUS:" IP ":" Port /
+ "OR:" IP ":" Port /
+ "CONSENSUS"
If "SKEW" is present, it's an estimate of how far we are from the
time declared in the source. (In other words, if we're an hour in
the past, the value is -3600.) "MIN_SKEW" is present, it's a lower
bound. If the source is a DIRSERV, we got the current time from a
connection to a dirserver. If the source is a NETWORKSTATUS, we
decided we're skewed because we got a v2 networkstatus from far in
- the future. If the source is CONSENSUS, we decided we're skewed
- because we got a networkstatus consensus from the future.
-
- {Controllers may want to warn the user if the skew is high, or if
- multiple skew messages appear at severity WARN. Controllers
- shouldn't blindly adjust the clock, since the more accurate source
- of skew info (DIRSERV) is currently unauthenticated.}
+ the future. If the source is OR, the skew comes from a NETINFO
+ cell from a connection to another relay. If the source is
+ CONSENSUS, we decided we're skewed because we got a networkstatus
+ consensus from the future.
+
+ {Tor should send this message to controllers when it thinks the
+ skew is so high that it will interfere with proper Tor operation.
+ Controllers shouldn't blindly adjust the clock, since the more
+ accurate source of skew info (DIRSERV) is currently
+ unauthenticated.}
BAD_LIBEVENT
"METHOD=" libevent method