diff options
Diffstat (limited to 'spec/tor-spec/negotiating-initializing-connections.md')
| -rw-r--r-- | spec/tor-spec/negotiating-initializing-connections.md | 11 |
1 files changed, 9 insertions, 2 deletions
diff --git a/spec/tor-spec/negotiating-initializing-connections.md b/spec/tor-spec/negotiating-initializing-connections.md index d281761..dd9be1d 100644 --- a/spec/tor-spec/negotiating-initializing-connections.md +++ b/spec/tor-spec/negotiating-initializing-connections.md @@ -1,4 +1,5 @@ <a id="tor-spec.txt-4"></a> + # Negotiating and initializing connections After Tor instances negotiate handshake with either the "renegotiation" or @@ -35,6 +36,7 @@ and did not permit any command other than VERSIONS as the first cell of the in-protocol handshake.] <a id="tor-spec.txt-4.1"></a> + ## Negotiating versions with VERSIONS cells There are multiple instances of the Tor link connection protocol. Any @@ -87,6 +89,7 @@ Link protocols differences are: ``` <a id="tor-spec.txt-4.2"></a> + ## CERTS cells The CERTS cell describes the keys that a Tor instance is claiming @@ -214,6 +217,7 @@ initiator has the ID it claims; to do so, the cells in 4.3 and 4.4 below must be exchanged. <a id="tor-spec.txt-4.3"></a> + ## AUTH_CHALLENGE cells An AUTH_CHALLENGE cell is a variable-length cell with the following @@ -236,6 +240,7 @@ accept. Only two authentication methods are defined right now: see 4.4.1 and 4.4.2 below. <a id="tor-spec.txt-4.4"></a> + ## AUTHENTICATE cells If an initiator wants to authenticate, it responds to the @@ -266,6 +271,7 @@ verified the certificates presented in the responder's CERTS cell, and authenticated the responder. <a id="tor-spec.txt-4.4.1"></a> + ### Link authentication type 1: RSA-SHA256-TLSSecret If AuthType is 1 (meaning "RSA-SHA256-TLSSecret"), then the @@ -315,7 +321,8 @@ claimed to have an Ed25519 identity. (There is no AuthType 2: It was reserved but never implemented.) <a id="tor-spec.txt-4.4.2"></a> -### Link authentication type 3: Ed25519-SHA256-RFC5705. + +### Link authentication type 3: Ed25519-SHA256-RFC5705 If AuthType is 3, meaning "Ed25519-SHA256-RFC5705", the Authentication field of the AuthType cell is as below: @@ -357,6 +364,7 @@ The server MUST ignore any extra bytes in the signed data after the RAND field. <a id="tor-spec.txt-4.5"></a> + ## NETINFO cells If version 2 or higher is negotiated, each party sends the other a @@ -400,4 +408,3 @@ since the other party can lie about the time or IP addresses it sees. 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.) - |