diff options
| -rw-r--r-- | doc/TODO.021 | 4 | ||||
| -rw-r--r-- | doc/spec/proposals/098-todo.txt | 6 | ||||
| -rw-r--r-- | doc/spec/tor-spec.txt | 5 |
3 files changed, 15 insertions, 0 deletions
diff --git a/doc/TODO.021 b/doc/TODO.021 index 08e94a0e8..1e1cc9412 100644 --- a/doc/TODO.021 +++ b/doc/TODO.021 @@ -187,6 +187,10 @@ N . Draft proposal for GeoIP aggregation (see external constraints *) their choices even before they have the descriptors; and so authorities can put in more accurate numbers in the future. + - Spec compliance: + - Make sure that clients could do the new handshake without sending any + certs, if they wanted. + - Tiny designs to write: - If a relay publishes a new descriptor with a significantly lower uptime or with a new IP address, then we should consider its current diff --git a/doc/spec/proposals/098-todo.txt b/doc/spec/proposals/098-todo.txt index 2365a861f..e891ea890 100644 --- a/doc/spec/proposals/098-todo.txt +++ b/doc/spec/proposals/098-todo.txt @@ -65,6 +65,12 @@ Any time: distribution. Need to think harder about allowing values less than 3, and there's a tradeoff between having a wide variance and performance. + - Clients currently use certs during TLS. Is this wise? It does make it + easier for servers to tell which NATted client is which. We could use a + seprate set of certs for each guard, I suppose, but generating so many + certs could get expensive. Omitting them entirely would make OP->OR + easier to tell from OR->OR. + Things that should change... B.1. ... but which will require backward-incompatible change diff --git a/doc/spec/tor-spec.txt b/doc/spec/tor-spec.txt index 8c6508f6e..8ab50242d 100644 --- a/doc/spec/tor-spec.txt +++ b/doc/spec/tor-spec.txt @@ -251,6 +251,11 @@ see tor-design.pdf. (As an exception, directory servers may try to stay connected to all of the ORs -- though this will be phased out for the Tor 0.1.2.x release.) + To avoid being trivially distinguished from servers, client-only Tor + instances are encouraged but not required to use a two-certificate chain + as well. Clients SHOULD NOT use keep using the same certificates when + their IP changes. Clients MAY send no certificates at all. + 3. Cell Packet format The basic unit of communication for onion routers and onion |