aboutsummaryrefslogtreecommitdiff
path: root/spec/rend-spec-v3/hidden-services-overview-preliminaries.md
diff options
context:
space:
mode:
Diffstat (limited to 'spec/rend-spec-v3/hidden-services-overview-preliminaries.md')
-rw-r--r--spec/rend-spec-v3/hidden-services-overview-preliminaries.md20
1 files changed, 10 insertions, 10 deletions
diff --git a/spec/rend-spec-v3/hidden-services-overview-preliminaries.md b/spec/rend-spec-v3/hidden-services-overview-preliminaries.md
index 382c732..cf16ff4 100644
--- a/spec/rend-spec-v3/hidden-services-overview-preliminaries.md
+++ b/spec/rend-spec-v3/hidden-services-overview-preliminaries.md
@@ -70,8 +70,8 @@ We write sequences of bytes in two ways:
```
We use INT_N(val) to denote the network (big-endian) encoding of the
-unsigned integer "val" in N bytes. For example, INT_4(1337) is [00 00
-05 39]. Values are truncated like so: val % (2 ^ (N * 8)). For example,
+unsigned integer "val" in N bytes. For example, INT_4(1337) is \[00 00
+05 39\]. Values are truncated like so: val % (2 ^ (N * 8)). For example,
INT_4(42) is 42 % 4294967296 (32 bit).
<a id="rend-spec-v3.txt-0.3"></a>
@@ -133,21 +133,21 @@ This specification uses the following cryptographic building blocks:
where k_len is htonll(len(k)).
```
- When we need a particular MAC key length below, we choose
- MAC_KEY_LEN=32 (256 bits).
+When we need a particular MAC key length below, we choose
+MAC_KEY_LEN=32 (256 bits).
For legacy purposes, we specify compatibility with older versions of
the Tor introduction point and rendezvous point protocols. These used
RSA1024, DH1024, AES128, and SHA1, as discussed in
rend-spec.txt.
-As in [proposal 220], all signatures are generated not over strings
+As in \[proposal 220\], all signatures are generated not over strings
themselves, but over those strings prefixed with a distinguishing
value.
<a id="rend-spec-v3.txt-0.4"></a>
-## Protocol building blocks [BUILDING-BLOCKS]
+## Protocol building blocks \[BUILDING-BLOCKS\]
In sections below, we need to transmit the locations and identities
of Tor nodes. We do so in the link identification format used by
@@ -162,8 +162,8 @@ EXTEND2 cells in the Tor protocol.
```
Link specifier types are as described in tor-spec.txt. Every set of
-link specifiers SHOULD include at minimum specifiers of type [00]
-(TLS-over-TCP, IPv4), [02] (legacy node identity) and [03] (ed25519
+link specifiers SHOULD include at minimum specifiers of type \[00\]
+(TLS-over-TCP, IPv4), \[02\] (legacy node identity) and \[03\] (ed25519
identity key). Sets of link specifiers without these three types
SHOULD be rejected.
@@ -308,8 +308,8 @@ editing help from
Tim Wilson-Brown ("teor"),
```
-[XXX Acknowledge the huge bunch of people working on 8106.]
-[XXX Acknowledge the huge bunch of people working on 8244.]
+\[XXX Acknowledge the huge bunch of people working on 8106.\]
+\[XXX Acknowledge the huge bunch of people working on 8244.\]
Please forgive me if I've missed you; please forgive me if I've
misunderstood your best ideas here too.