aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2004-04-07 21:36:03 +0000
committerNick Mathewson <nickm@torproject.org>2004-04-07 21:36:03 +0000
commit8169da5c30cbea7c73f5d0f56d1a507703aa48cc (patch)
tree585eb5c25e87798ee35f2ece02bc52bd86d3fadf /doc
parent7c7301fe926a9ca0f48ed645f3c4a92466477ce1 (diff)
downloadtor-8169da5c30cbea7c73f5d0f56d1a507703aa48cc.tar
tor-8169da5c30cbea7c73f5d0f56d1a507703aa48cc.tar.gz
Don't use Tor version 0.0.5 for intro/rendezvous points. (We don't need
to worry about 0.0.4 or earlier, because nobody is running them any more.) svn:r1533
Diffstat (limited to 'doc')
-rw-r--r--doc/TODO2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/TODO b/doc/TODO
index 8e707f4c9..f371d4507 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -148,7 +148,7 @@ Rendezvous service:
protocol, how do we deal? have nodes parse the tor version field?
force an upgrade? simply be more robust against useless nodes?
o should expire rend streams when too much time has passed
- - should make failed rend/intro circs count toward alice's
+ o should make failed rend/intro circs count toward alice's
num_failed circs, to prevent madness when we're offline (But
don't count failed rend circs toward Bob's total, or Alice
can bork him.)