torproject/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-12-06 19:41:15 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

minor updates from my sandbox

Browse Source 
svn:r13724
This commit is contained in:
Roger Dingledine
2008-02-25 06:47:15 +00:00
parent d1cb225c89
commit 91a6a69070
2 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/design-paper/roadmap-future.pdf
BIN
View File
Binary file not shown.
doc/design-paper/roadmap-future.tex
+5 -5
View File
@@ -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.