[or-cvs] Be more clear about fixing unknown rendezvous points. (ow)

[Nick Mathewson]

Update of /home/or/cvsroot/tor/doc
In directory moria:/tmp/cvs-serv12908/doc

Modified Files:
	TODO 
Log Message:
Be more clear about fixing unknown rendezvous points. (ow)

Index: TODO
===================================================================
RCS file: /home/or/cvsroot/tor/doc/TODO,v
retrieving revision 1.326
retrieving revision 1.327
diff -u -d -r1.326 -r1.327
--- TODO	19 Jun 2005 22:39:14 -0000	1.326
+++ TODO	20 Jun 2005 00:10:31 -0000	1.327
@@ -66,6 +66,7 @@
       immediately, since tor will exit right after.
       o Implement
       - Test, debug
+    - Allow EXTENDCIRCUIT to unknown server.
     . Switch example controllers to use new protocol
       . Python
         o Implement main controller interface
@@ -81,12 +82,13 @@
     first place.)  Also, we should audit all users of get_pending_bytes().)
     - Make it harder to circumvent bandwidth caps: look at number of bytes
       sent across sockets, not number sent inside TLS stream.
-  - Handle rendezvousing with unverified nodes.
-    - Specify: Stick rendezvous point's key in INTRODUCE cell.
-      Bob should _always_ use key from INTRODUCE cell.
-    - Change to new rendezvous introduction cell format.  (It's currently #if
-      0'd out).  Unless we already did that.
-    - Implement.
+N - Handle rendezvousing with unverified nodes.
+    o Specify: Stick rendezvous point's address and port in INTRODUCE cell.
+    - Handle new format.
+      - Parse and generate new format (#if0 out the logic to generate it.)
+      - Support to extend circuit/target circuit to a chosen combination of
+        addr/port/ID/onionkey
+    - Verify that new code works.
   - it looks like tor_assert writes to stderr. what happens if
     stderr was closed and is now something else? uh.
   - christian grothoff's attack of infinite-length circuit.