diff options
| author | Roger Dingledine <arma@torproject.org> | 2017-05-14 01:12:51 -0400 |
|---|---|---|
| committer | Roger Dingledine <arma@torproject.org> | 2017-05-14 01:12:51 -0400 |
| commit | f44a8ce77264229e2f9a67eab5fa9928e692dec0 (patch) | |
| tree | 7218d46b59317f24ac71ade7497467356e2e2e55 /tor-spec.txt | |
| parent | bea0a22d10196e3d137e41bbed13f19d7c27e056 (diff) | |
| download | torspec-f44a8ce77264229e2f9a67eab5fa9928e692dec0.tar.gz torspec-f44a8ce77264229e2f9a67eab5fa9928e692dec0.zip | |
resolve a confusing typo about the v3 link handshake
unless it was meant to be this way, and I'm the one who got confused?
Diffstat (limited to 'tor-spec.txt')
| -rw-r--r-- | tor-spec.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tor-spec.txt b/tor-spec.txt index 927173b..7501246 100644 --- a/tor-spec.txt +++ b/tor-spec.txt @@ -192,7 +192,7 @@ see tor-design.pdf. way, "renegotiation", the responder provides a single certificate, and the initiator immediately performs a TLS renegotiation. (This is supported in Tor 0.2.0.21 and later.) And in the third way, - "in-protocol", the initial TLS renegotiation completes, and the + "in-protocol", the initial TLS negotiation completes, and the parties bootstrap themselves to mutual authentication via use of the Tor protocol without further TLS handshaking. (This is supported in 0.2.3.6-alpha and later.) |