[or-cvs] nick suggests that the hello cell should have both server I...
arma at seul.org
arma at seul.org
Mon Jul 17 05:12:56 UTC 2006
Update of /home2/or/cvsroot/tor/doc
In directory moria:/home/arma/work/onion/cvs/tor/doc
nick suggests that the hello cell should have both server IP and
client IP. he's right.
RCS file: /home2/or/cvsroot/tor/doc/tor-spec.txt,v
retrieving revision 1.119
retrieving revision 1.120
diff -u -p -d -r1.119 -r1.120
--- tor-spec.txt 15 Jul 2006 05:50:22 -0000 1.119
+++ tor-spec.txt 17 Jul 2006 05:12:54 -0000 1.120
@@ -748,9 +748,8 @@ when do we rotate which keys (tls, link,
Version [1 byte]
Timestamp [4 bytes]
- Number of addresses [1 byte]
- Addresses [variable]
+ Server-side address [variable]
+ Client-side address [variable]
Version is the "link version", and dictates what types and formats
of cells can be sent/received. It should be 1. A Tor connection is
@@ -760,12 +759,15 @@ when do we rotate which keys (tls, link,
Timestamp is the OR's current Unix time (GMT).
Each address contains Type/Length/Value as used in Section 5.4.
- This section lists all addresses that the OR has published and is
- listening to now -- we include them to block a man-in-the-middle
+ The first address is the one that the OR has published and is
+ listening to now -- we include it to block a man-in-the-middle
attack on TLS that lets an attacker bounce traffic through his own
computers to enable timing and packet-counting attacks.
[Do we want to provide just one address? Do we want to be more
general by accepting netmasks or something? -RD]
+ The second address is the one that the client OP or OR has used to
+ connect to the server -- it can be used to learn what your IP address
+ is if you have no other hints.
If we receive a HELLO cell with a version we do not recognize, we drop
it. If we receive a HELLO cell with a version that is older than the
More information about the tor-commits