Explorar el Código

update the TODO to reflect recent commits

svn:r882
Roger Dingledine hace 20 años
padre
commit
3865a8a888
Se han modificado 3 ficheros con 10 adiciones y 8 borrados
  1. 7 5
      doc/TODO
  2. 1 1
      doc/tor-spec.txt
  3. 2 2
      doc/tor.1.in

+ 7 - 5
doc/TODO

@@ -1,6 +1,4 @@
 improve how it behaves when i remove a line from the approved-routers files
 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.)
 on hup, retry_all_connections (plus binding? and closing i guess. hm.)
 
 
 Legend:
 Legend:
@@ -16,9 +14,11 @@ ARMA    - arma claims
         X Abandoned
         X Abandoned
 
 
 For 0.0.2pre15:
 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:
 For 0.0.2pre14:
         o More flexible exit policies (18.*, 18.0.0.0/8)
         o More flexible exit policies (18.*, 18.0.0.0/8)
@@ -101,6 +101,8 @@ On-going
         . Unit tests
         . Unit tests
 
 
 Mid-term:
 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
         - Are there anonymity issues with sequential streamIDs? Sequential
           circIDs? Eg an attacker can learn how many there have been.
           circIDs? Eg an attacker can learn how many there have been.
           The fix is to initialize them randomly rather than at 1.
           The fix is to initialize them randomly rather than at 1.

+ 1 - 1
doc/tor-spec.txt

@@ -319,7 +319,7 @@ which reveals the downstream node.
          Relay command           [1 byte]
          Relay command           [1 byte]
          Stream ID               [7 bytes]
          Stream ID               [7 bytes]
 
 
-   The recognized relay commands are:
+   The relay commands are:
          1 -- RELAY_BEGIN
          1 -- RELAY_BEGIN
          2 -- RELAY_DATA
          2 -- RELAY_DATA
          3 -- RELAY_END
          3 -- RELAY_END

+ 2 - 2
doc/tor.1.in

@@ -18,14 +18,14 @@ routers"). Users bounce their tcp streams -- web traffic, ftp, ssh, etc --
 around the routers, and recipients, observers, and even the routers
 around the routers, and recipients, observers, and even the routers
 themselves have difficulty tracking the source of the stream.
 themselves have difficulty tracking the source of the stream.
 .SH OPTIONS
 .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
 \fB-h, -help\fP
 Display a short help message and exit.
 Display a short help message and exit.
 .TP
 .TP
 \fB-f \fR\fIFILE\fP
 \fB-f \fR\fIFILE\fP
 FILE contains further "option value" pairs. (Default: @CONFDIR@/torrc)
 FILE contains further "option value" pairs. (Default: @CONFDIR@/torrc)
 .TP
 .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
 \fBloglevel debug|info|warn|err\fP
 Set the verboseness level of the primary log. (Default: warn)
 Set the verboseness level of the primary log. (Default: warn)
 .TP
 .TP