diff options
Diffstat (limited to 'spec/rend-spec-v3/rendezvous-protocol.md')
| -rw-r--r-- | spec/rend-spec-v3/rendezvous-protocol.md | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/spec/rend-spec-v3/rendezvous-protocol.md b/spec/rend-spec-v3/rendezvous-protocol.md index 316bcf2..683d9e4 100644 --- a/spec/rend-spec-v3/rendezvous-protocol.md +++ b/spec/rend-spec-v3/rendezvous-protocol.md @@ -21,12 +21,12 @@ but use an anonymous 3-hop circuit if: <a id="rend-spec-v3.txt-4.1"></a> -## Establishing a rendezvous point [EST_REND_POINT] +## Establishing a rendezvous point \[EST_REND_POINT\] The client sends the rendezvous point a RELAY_COMMAND_ESTABLISH_RENDEZVOUS cell containing a 20-byte value. -RENDEZVOUS_COOKIE [20 bytes] +RENDEZVOUS_COOKIE \[20 bytes\] Rendezvous points MUST ignore any extra bytes in an ESTABLISH_RENDEZVOUS cell. (Older versions of Tor did not.) @@ -50,7 +50,7 @@ connect to a hidden service. <a id="rend-spec-v3.txt-4.2"></a> -## Joining to a rendezvous point [JOIN_REND] +## Joining to a rendezvous point \[JOIN_REND\] To complete a rendezvous, the hidden service host builds a circuit to the rendezvous point and sends a RENDEZVOUS1 cell containing: @@ -62,8 +62,8 @@ the rendezvous point and sends a RENDEZVOUS1 cell containing: ``` where RENDEZVOUS_COOKIE is the cookie suggested by the client during the -introduction (see [PROCESS_INTRO2]) and HANDSHAKE_INFO is defined in -[NTOR-WITH-EXTRA-DATA]. +introduction (see \[PROCESS_INTRO2\]) and HANDSHAKE_INFO is defined in +\[NTOR-WITH-EXTRA-DATA\]. If the cookie matches the rendezvous cookie set on any not-yet-connected circuit on the rendezvous point, the rendezvous @@ -73,7 +73,7 @@ client containing the HANDSHAKE_INFO field of the RENDEZVOUS1 cell. Upon receiving the RENDEZVOUS2 cell, the client verifies that HANDSHAKE_INFO correctly completes a handshake. To do so, the client parses SERVER_PK from HANDSHAKE_INFO and reverses the final operations of section -[NTOR-WITH-EXTRA-DATA] as shown here: +\[NTOR-WITH-EXTRA-DATA\] as shown here: ```text rend_secret_hs_input = EXP(Y,x) | EXP(B,x) | AUTH_KEY | B | X | Y | PROTOID @@ -112,16 +112,16 @@ keys for the ORs in Alice's side of the circuit, then decrypts them with Kb, and checks integrity with Db. Bob's OP does the same, with Kf and Kb interchanged. -[TODO: Should we encrypt HANDSHAKE_INFO as we did INTRODUCE2 +\[TODO: Should we encrypt HANDSHAKE_INFO as we did INTRODUCE2 contents? It's not necessary, but it could be wise. Similarly, we -should make it extensible.] +should make it extensible.\] <a id="rend-spec-v3.txt-4.3"></a> ## Using legacy hosts as rendezvous points -[This section is obsolete and refers to a workaround for now-obsolete Tor -relay versions. It is included for historical reasons.] +\[This section is obsolete and refers to a workaround for now-obsolete Tor +relay versions. It is included for historical reasons.\] The behavior of ESTABLISH_RENDEZVOUS is unchanged from older versions of this protocol, except that relays should now ignore unexpected |