[or-cvs] r14336: Remove tracked-elsewhere issues. (in tor/trunk: . doc)

nickm at seul.org nickm at seul.org
Wed Apr 9 20:31:57 UTC 2008


Author: nickm
Date: 2008-04-09 16:31:56 -0400 (Wed, 09 Apr 2008)
New Revision: 14336

Modified:
   tor/trunk/
   tor/trunk/doc/TODO
Log:
 r19276 at catbus:  nickm | 2008-04-09 16:25:02 -0400
 Remove tracked-elsewhere issues.



Property changes on: tor/trunk
___________________________________________________________________
 svk:merge ticket from /tor/trunk [r19276] on 8246c3cf-6607-4228-993b-4d95d33730f1

Modified: tor/trunk/doc/TODO
===================================================================
--- tor/trunk/doc/TODO	2008-04-09 20:31:54 UTC (rev 14335)
+++ tor/trunk/doc/TODO	2008-04-09 20:31:56 UTC (rev 14336)
@@ -446,24 +446,6 @@
   - Some mechanism for specifying that we want to stop using a cached
     bridge.
 
-* * * *
-
-Removing these because they're tracked elsewhere:
-
-  - we try to build 4 test circuits to break them over different
-    servers. but sometimes our entry node is the same for multiple
-    test circuits. this defeats the point.
-    [ TRACKED IN BUG 654 ]
-
-  d Limit to 2 dir, 2 OR, N SOCKS connections per IP.
-    - Or maybe close connections from same IP when we get a lot from one.
-    - Or maybe block IPs that connect too many times at once.
-    [ Same as bug 469 ]
-
-  - more strategies for distributing bridge addresses in a way that
-    doesn't rely on knowing somebody who runs a bridge for you.
-    [ In birdgedb TODO ]
-
 =======================================================================
 
 Future versions:



More information about the tor-commits mailing list