aboutsummaryrefslogtreecommitdiff
path: root/spec/tor-spec/negotiating-channels.md
diff options
context:
space:
mode:
Diffstat (limited to 'spec/tor-spec/negotiating-channels.md')
-rw-r--r--spec/tor-spec/negotiating-channels.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/spec/tor-spec/negotiating-channels.md b/spec/tor-spec/negotiating-channels.md
index 2b8ebd6..ee5e974 100644
--- a/spec/tor-spec/negotiating-channels.md
+++ b/spec/tor-spec/negotiating-channels.md
@@ -37,7 +37,7 @@ the in-protocol handshake.\]
<a id="tor-spec.txt-4.1"></a>
-## Negotiating versions with VERSIONS cells
+## Negotiating versions with VERSIONS cells {#VERSIONS-cells}
There are multiple instances of the Tor link connection protocol. Any
connection negotiated using the "certificates up front" handshake (see
@@ -90,7 +90,7 @@ Link protocols differences are:
<a id="tor-spec.txt-4.2"></a>
-## CERTS cells
+## CERTS cells {#CERTS-cells}
The CERTS cell describes the keys that a Tor instance is claiming
to have. It is a variable-length cell. Its payload format is:
@@ -272,7 +272,7 @@ cell, and authenticated the responder.
<a id="tor-spec.txt-4.4.1"></a>
-### Link authentication type 1: RSA-SHA256-TLSSecret
+### Link authentication type 1: RSA-SHA256-TLSSecret {#RSA-SHA256-TLSSecret}
If AuthType is 1 (meaning "RSA-SHA256-TLSSecret"), then the
Authentication field of the AUTHENTICATE cell contains the following:
@@ -322,7 +322,7 @@ claimed to have an Ed25519 identity.
<a id="tor-spec.txt-4.4.2"></a>
-### Link authentication type 3: Ed25519-SHA256-RFC5705
+### Link authentication type 3: Ed25519-SHA256-RFC5705 {#Ed25519-SHA256-RFC5705}
If AuthType is 3, meaning "Ed25519-SHA256-RFC5705", the
Authentication field of the AuthType cell is as below: