diff options
Diffstat (limited to 'spec/tor-spec/negotiating-channels.md')
| -rw-r--r-- | spec/tor-spec/negotiating-channels.md | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/spec/tor-spec/negotiating-channels.md b/spec/tor-spec/negotiating-channels.md index 29ad91f..f5cd610 100644 --- a/spec/tor-spec/negotiating-channels.md +++ b/spec/tor-spec/negotiating-channels.md @@ -7,23 +7,23 @@ After Tor instances negotiate handshake with either the "renegotiation" or the Tor connection and make it "open" and usable for circuits. When the renegotiation handshake is used, both parties immediately -send a VERSIONS cell (4.1 below), and after negotiating a link -protocol version (which will be 2), each send a NETINFO cell (4.5 -below) to confirm their addresses and timestamps. No other intervening +send a [VERSIONS cell](#VERSIONS-cell), and after negotiating a link +protocol version (which will be 2), each send a [NETINFO cell](#NETINFO-cells) +to confirm their addresses and timestamps. No other intervening cell types are allowed. When the in-protocol handshake is used, the initiator sends a VERSIONS cell to indicate that it will not be renegotiating. The -responder sends a VERSIONS cell, a CERTS cell (4.2 below) to give the +responder sends a VERSIONS cell, a [CERTS cell](#CERTS-cells) to give the initiator the certificates it needs to learn the responder's -identity, an AUTH_CHALLENGE cell (4.3) that the initiator must include -as part of its answer if it chooses to authenticate, and a NETINFO -cell (4.5). As soon as it gets the CERTS cell, the initiator knows +identity, an [AUTH_CHALLENGE cell](#AUTH-CHALLENGE-cells) that the initiator must include +as part of its answer if it chooses to authenticate, and a +[NETINFO cell](#NETINFO-cells). As soon as it gets the CERTS cell, the initiator knows whether the responder is correctly authenticated. At this point the initiator behaves differently depending on whether it wants to authenticate or not. If it does not want to authenticate, it MUST send a NETINFO cell. If it does want to authenticate, it MUST send a -CERTS cell, an AUTHENTICATE cell (4.4), and a NETINFO. When this +CERTS cell, an [AUTHENTICATE cell](#AUTHENTICATE-cells), and a NETINFO. When this handshake is in use, the first cell must be VERSIONS, VPADDING, or AUTHORIZE, and no other cell type is allowed to intervene besides those specified, except for VPADDING cells. @@ -41,7 +41,7 @@ the in-protocol handshake.\] There are multiple instances of the Tor link connection protocol. Any connection negotiated using the "certificates up front" handshake (see -section 2 above) is "version 1". In any connection where both parties +[Connections](./channels.md#connections)) is "version 1". In any connection where both parties have behaved as in the "renegotiation" handshake, the link protocol version must be 2. In any connection where both parties have behaved as in the "in-protocol" handshake, the link protocol must be 3 or higher. |