[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[or-cvs] r12230: (in tor/trunk: . doc)



Author: nickm
Date: 2007-10-27 11:44:44 -0400 (Sat, 27 Oct 2007)
New Revision: 12230

Modified:
   tor/trunk/
   tor/trunk/doc/TODO
Log:
 r16209@catbus:  nickm | 2007-10-27 11:42:24 -0400
 



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

Modified: tor/trunk/doc/TODO
===================================================================
--- tor/trunk/doc/TODO	2007-10-27 14:52:14 UTC (rev 12229)
+++ tor/trunk/doc/TODO	2007-10-27 15:44:44 UTC (rev 12230)
@@ -23,6 +23,9 @@
     - Support for preconfigured mirror lists
       - Use a pre-shipped fallback consensus.
     - Download consensuses (et al) via if-modified-since
+      - Implement backend support for sending if-modified-since
+      - Use it for consensuses.
+      - Use it for certificates
     o Saner TLS rotation
       o Bump up OR the "connection timeout" value to be 1.5
 	circuit dirtiness interval.
@@ -39,6 +42,24 @@
     D 118 if feasible and obvious
     D Maintain a skew estimate and use ftime consistently.
     - 105+TLS, if possible.
+      - 105 only
+        - Need to get a finished proposal 105
+        - "Pick a version" function
+        - Have a 'waiting_for_version' state.
+        - Store version in or_connection_t.
+        - Generate netinfo cells
+        - Accept netinfo cells
+        - Version negotiation: send a version cell and enter
+          waiting-for-version; when version cell arrives, pick version
+          and send netinfo and be "open".
+        - On netinfo, warn if there's skew from a server.
+        - Handle IP addresses in netinfo properly.
+      - TLS only
+        - Need to get a finished TLS normalization proposal
+        - Revised authentication.
+        - Revised handshake.
+        - Have a 'waiting_for_authentication' state.
+        - Only do version negotiation if we use the normalized TLS.
     - Skew issues:
       - if you load (nick says receive/set/anything) a consensus that's
         in the future, then log about skew.