[tor-dev] [PATCH] Fix minor typos in tor-spec.txt
martink at posteo.de
Tue May 13 17:50:22 UTC 2014
feel free to ignore this. I don't know if you take typo fixes. But why not
report them while reading.
tor-spec.txt | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/tor-spec.txt b/tor-spec.txt
index 2555af4..86ee849 100644
@@ -501,7 +501,7 @@ see tor-design.pdf.
highest number contained both in the VERSIONS cell they sent and in the
versions cell they received. If they have no such version in common,
they cannot communicate and MUST close the connection. Either party MUST
- close the connection of the versions cell is not well-formed (for example,
+ close the connection if the versions cell is not well-formed (for example,
if it contains an odd number of bytes).
Since the version 1 link protocol does not use the "renegotiation"
@@ -648,8 +648,8 @@ see tor-design.pdf.
To check the AUTHENTICATE cell, a responder checks that all fields
from TYPE through TLSSECRETS contain their unique
correct values as described above, and then verifies the signature.
- signature. The server MUST ignore any extra bytes in the signed
- data after the SHA256 hash.
+ The server MUST ignore any extra bytes in the signed data after
+ the SHA256 hash.
Initiators MUST NOT send an AUTHENTICATE cell before they have
verified the certificates presented in the responder's CERTS
@@ -751,7 +751,7 @@ see tor-design.pdf.
another, it chooses from only one half of the possible values based
on the ORs' public identity keys. In link protocol version 3 or
lower, if the sending node has a lower key, it chooses a CircID with
- an MSB of 0; otherwise, it chooses a CircID with an MSB of 1. (Public
+ a MSB of 0; otherwise, it chooses a CircID with a MSB of 1. (Public
keys are compared numerically by modulus.)
In link protocol version 4 or higher, whichever node initiated the
@@ -1087,7 +1087,7 @@ see tor-design.pdf.
bytes sent between Alice and Bob (assuming Alice was not already
connected to Bob.)
- To prevent this, when an OR we gets an extend request, it SHOULD use an
+ To prevent this, when an OR gets an extend request, it SHOULD use an
existing OR connection if the ID matches, and ANY of the following
- The IP matches the requested IP.
More information about the tor-dev