aboutsummaryrefslogtreecommitdiff
path: root/doc/design-paper
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2008-02-25 06:47:15 +0000
committerRoger Dingledine <arma@torproject.org>2008-02-25 06:47:15 +0000
commit91a6a690702cdf001d8e060086b0d849ac10a3ca (patch)
tree853d6249a97663ac464c474578127ddeb5feb7a7 /doc/design-paper
parentd1cb225c8991a72a1b921f453051a44ae981d974 (diff)
downloadtor-91a6a690702cdf001d8e060086b0d849ac10a3ca.tar
tor-91a6a690702cdf001d8e060086b0d849ac10a3ca.tar.gz
minor updates from my sandbox
svn:r13724
Diffstat (limited to 'doc/design-paper')
-rw-r--r--doc/design-paper/roadmap-future.pdfbin64900 -> 72297 bytes
-rw-r--r--doc/design-paper/roadmap-future.tex10
2 files changed, 5 insertions, 5 deletions
diff --git a/doc/design-paper/roadmap-future.pdf b/doc/design-paper/roadmap-future.pdf
index 9d83a55dd..8300ce19c 100644
--- a/doc/design-paper/roadmap-future.pdf
+++ b/doc/design-paper/roadmap-future.pdf
Binary files differ
diff --git a/doc/design-paper/roadmap-future.tex b/doc/design-paper/roadmap-future.tex
index 2b13723d2..4ab240f97 100644
--- a/doc/design-paper/roadmap-future.tex
+++ b/doc/design-paper/roadmap-future.tex
@@ -147,12 +147,12 @@ in this state so they can run software that will only run in the past.
Before Tor 0.1.1.x, Tor clients would still function if their clock was
wildly off --- they simply got a copy of the directory and believed it.
-Starting in Tor 0.1.2.x, the clients only believed networkstatus documents
-that they believed to be recent, so clients with extremely wrong clocks
-stopped working. (This bug has been an unending source of vague and
-confusing bug reports.)
+Starting in Tor 0.1.1.x (and even moreso in Tor 0.2.0.x), the clients
+only use networkstatus documents that they believe to be recent, so
+clients with extremely wrong clocks no longer work. (This bug has been
+an unending source of vague and confusing bug reports.)
-Step one is for clients to recognize when all the directory material
+The first step is for clients to recognize when all the directory material
they're fetching has roughly the same offset from their current time,
and then automatically correct for it.