diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/design-paper/roadmap-future.pdf | bin | 64900 -> 72297 bytes | |||
| -rw-r--r-- | doc/design-paper/roadmap-future.tex | 10 |
2 files changed, 5 insertions, 5 deletions
diff --git a/doc/design-paper/roadmap-future.pdf b/doc/design-paper/roadmap-future.pdf Binary files differindex 9d83a55dda..8300ce19c9 100644 --- a/doc/design-paper/roadmap-future.pdf +++ b/doc/design-paper/roadmap-future.pdf diff --git a/doc/design-paper/roadmap-future.tex b/doc/design-paper/roadmap-future.tex index 2b13723d2d..4ab240f977 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. |