[or-cvs] update the TODO to reflect recent commits

[Roger Dingledine]

Update of /home/or/cvsroot/doc
In directory moria.mit.edu:/home2/arma/work/onion/cvs/doc

Modified Files:
	tor.1.in TODO tor-spec.txt 
Log Message:
update the TODO to reflect recent commits


Index: tor.1.in
===================================================================
RCS file: /home/or/cvsroot/doc/tor.1.in,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- tor.1.in	20 Nov 2003 20:56:52 -0000	1.1
+++ tor.1.in	3 Dec 2003 10:44:11 -0000	1.2
@@ -18,13 +18,13 @@
 around the routers, and recipients, observers, and even the routers
 themselves have difficulty tracking the source of the stream.
 .SH OPTIONS
-Options can be specified either on the commandline (\fI--option value\fR), or in the configuration file (\fIoption value\fR).
-.TP
 \fB-h, -help\fP
 Display a short help message and exit.
 .TP
 \fB-f \fR\fIFILE\fP
 FILE contains further "option value" pairs. (Default: @CONFDIR@/torrc)
+.TP
+Other options can be specified either on the commandline (\fI--option value\fR), or in the configuration file (\fIoption value\fR).
 .TP
 \fBloglevel debug|info|warn|err\fP
 Set the verboseness level of the primary log. (Default: warn)

Index: TODO
===================================================================
RCS file: /home/or/cvsroot/doc/TODO,v
retrieving revision 1.44
retrieving revision 1.45
diff -u -d -r1.44 -r1.45
--- TODO	2 Dec 2003 18:20:31 -0000	1.44
+++ TODO	3 Dec 2003 10:44:11 -0000	1.45
@@ -1,6 +1,4 @@
 improve how it behaves when i remove a line from the approved-routers files
-    - Rotate tls-level connections -- make new ones, expire old ones.
-      Nick, can you remember why we wanted to do this?
 on hup, retry_all_connections (plus binding? and closing i guess. hm.)
 
 Legend:
@@ -16,9 +14,11 @@
         X Abandoned
 
 For 0.0.2pre15:
-        - don't pick exit nodes which will certainly reject all things.
-        - don't pick nodes that the directory says are down
-        - choose randomly from running dirservers, not just first one
+        o don't pick exit nodes which will certainly reject all things.
+        o don't pick nodes that the directory says are down
+        o choose randomly from running dirservers, not just first one
+        o install the man page
+        o warn when client-side tries an address/port which no router in the dir accepts.
 
 For 0.0.2pre14:
         o More flexible exit policies (18.*, 18.0.0.0/8)
@@ -101,6 +101,8 @@
         . Unit tests
 
 Mid-term:
+        - Rotate tls-level connections -- make new ones, expire old ones.
+          So we get actual key rotation, not just symmetric key rotation
         - Are there anonymity issues with sequential streamIDs? Sequential
           circIDs? Eg an attacker can learn how many there have been.
           The fix is to initialize them randomly rather than at 1.

Index: tor-spec.txt
===================================================================
RCS file: /home/or/cvsroot/doc/tor-spec.txt,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -d -r1.43 -r1.44
--- tor-spec.txt	11 Nov 2003 02:36:50 -0000	1.43
+++ tor-spec.txt	3 Dec 2003 10:44:11 -0000	1.44
@@ -319,7 +319,7 @@
          Relay command           [1 byte]
          Stream ID               [7 bytes]
 
-   The recognized relay commands are:
+   The relay commands are:
          1 -- RELAY_BEGIN
          2 -- RELAY_DATA
          3 -- RELAY_END