From 3865a8a88895c3c386c6aa89bd23cfccbca4dbf2 Mon Sep 17 00:00:00 2001 From: Roger Dingledine Date: Wed, 3 Dec 2003 10:44:11 +0000 Subject: [PATCH] update the TODO to reflect recent commits svn:r882 --- doc/TODO | 12 +++++++----- doc/tor-spec.txt | 2 +- doc/tor.1.in | 4 ++-- 3 files changed, 10 insertions(+), 8 deletions(-) diff --git a/doc/TODO b/doc/TODO index 4bd40f4281..a6696f3241 100644 --- a/doc/TODO +++ b/doc/TODO @@ -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 @@ ARMA - arma claims 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 @@ On-going . 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. diff --git a/doc/tor-spec.txt b/doc/tor-spec.txt index 39b6291924..490cf48dc0 100644 --- a/doc/tor-spec.txt +++ b/doc/tor-spec.txt @@ -319,7 +319,7 @@ which reveals the downstream node. 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 diff --git a/doc/tor.1.in b/doc/tor.1.in index da9c2031c6..c9823df769 100644 --- a/doc/tor.1.in +++ b/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 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) .TP -- 2.11.4.GIT