diff options
| -rw-r--r-- | proposals/149-using-netinfo-data.txt | 5 | ||||
| -rw-r--r-- | tor-spec.txt | 8 |
2 files changed, 8 insertions, 5 deletions
diff --git a/proposals/149-using-netinfo-data.txt b/proposals/149-using-netinfo-data.txt index cf2945a..0ad663c 100644 --- a/proposals/149-using-netinfo-data.txt +++ b/proposals/149-using-netinfo-data.txt @@ -2,9 +2,12 @@ Filename: 149-using-netinfo-data.txt Title: Using data from NETINFO cells Author: Nick Mathewson Created: 2-Jul-2008 -Status: Draft +Status: Superseded Target: 0.2.1.x +[Partially done: we do the anti-MITM part. Not entirely done: we don't do +the time part.] + Overview Current Tor versions send signed IP and timestamp information in diff --git a/tor-spec.txt b/tor-spec.txt index cb4c70d..9c45a36 100644 --- a/tor-spec.txt +++ b/tor-spec.txt @@ -366,11 +366,11 @@ see tor-design.pdf. Implementations MAY use the timestamp value to help decide if their clocks are skewed. Initiators MAY use "other OR's address" to help learn which address their connections are originating from, if they do - not know it. Initiators SHOULD use "this OR's address" to make sure - that they have connected to another OR at its canonical address. - - [As of 0.2.0.23-rc, implementations use none of the above values.] + not know it. [As of 0.2.3.1-alpha, nodes use neither of these values.] + Initiators SHOULD use "this OR's address" to make sure + that they have connected to another OR at its canonical address. + (See 5.3.1 below.) 5. Circuit management |