diff options
| author | Jim Newsome <jnewsome@torproject.org> | 2023-11-09 11:05:05 -0600 |
|---|---|---|
| committer | Jim Newsome <jnewsome@torproject.org> | 2023-11-09 18:45:20 -0600 |
| commit | b74a68361735b4a7c60ed395f417d22914986ae2 (patch) | |
| tree | 70505487c7ef84aa0ad1bb7f35be9dfbcb41617d /proposals | |
| parent | 72722037eed69e1a05d204c62ed9629f5b571b85 (diff) | |
| download | torspec-b74a68361735b4a7c60ed395f417d22914986ae2.tar.gz torspec-b74a68361735b4a7c60ed395f417d22914986ae2.zip | |
Escape brackets that aren't meant to be reference-links
Diffstat (limited to 'proposals')
| -rw-r--r-- | proposals/332-ntor-v3-with-extra-data.md | 4 | ||||
| -rw-r--r-- | proposals/339-udp-over-tor.md | 2 |
2 files changed, 3 insertions, 3 deletions
diff --git a/proposals/332-ntor-v3-with-extra-data.md b/proposals/332-ntor-v3-with-extra-data.md index 58a3bf3..10f0dd4 100644 --- a/proposals/332-ntor-v3-with-extra-data.md +++ b/proposals/332-ntor-v3-with-extra-data.md @@ -47,7 +47,7 @@ The client knows: * An optional "verification" string. The relay knows: - * A set of [(b,B)...] "onion key" keypairs. One of them is + * A set of \[(b,B)...\] "onion key" keypairs. One of them is "current", the others are outdated, but still valid. * ID: Its own identity. * A function for computing a server message SM, based on a given @@ -398,7 +398,7 @@ client sends a message, with type `CIRCWINDOW_INC`, containing a two-byte integer equal to `circwindow_inc_dflt`. The relay rejects the message if the value given is outside of the -[`circwindow_inc_min`, `circwindow_inc_max`] range. Otherwise, it +\[`circwindow_inc_min`, `circwindow_inc_max`\] range. Otherwise, it accepts it, and replies with the same message that the client sent. # X.2: Test vectors diff --git a/proposals/339-udp-over-tor.md b/proposals/339-udp-over-tor.md index 5993bdc..12de0c6 100644 --- a/proposals/339-udp-over-tor.md +++ b/proposals/339-udp-over-tor.md @@ -264,7 +264,7 @@ I'd suggest we do it. 1. We would add a new "`FLAG_UNCONNECTED`" flag for `CONNECT_UDP` messages. -2. We would designate the ANY addresses 0.0.0.0:0 and [::]:0 as permitted in +2. We would designate the ANY addresses 0.0.0.0:0 and \[::\]:0 as permitted in `CONNECT_UDP` messages, and as indicating unconnected sockets. These would be only permitted along with the `FLAG_UNCONNECTED` flag, and not permitted otherwise. |