diff options
| author | Emil Engler <me@emilengler.com> | 2022-12-22 19:31:01 +0100 |
|---|---|---|
| committer | Emil Engler <me@emilengler.com> | 2022-12-22 19:31:01 +0100 |
| commit | 31c325434ea540f1ca27bc10e88fb13ad960a16b (patch) | |
| tree | b5f19f4b6c34561ebe7675cddeab5a12e5078f5d /tor-spec.txt | |
| parent | 7116c9cdaba248aae07a3f1d0e15d9dd102f62c5 (diff) | |
| download | torspec-31c325434ea540f1ca27bc10e88fb13ad960a16b.tar.gz torspec-31c325434ea540f1ca27bc10e88fb13ad960a16b.zip | |
tor-spec: fix ambitious formulation in VERSIONS
This commit fixes an ambitious formulation within the definition of the
VERSIONS cells. It says, that a VERSIONS cell with an odd number of
bytes is invalid. This statement is not true, because the CircID (2
bytes for VERSIONS cells), Command (1 byte) and Length (2 byte) make up
5 bytes, which is an odd number. Adding an odd number to an even number
of bytes (the payload in this case) always results in an odd number.
Diffstat (limited to 'tor-spec.txt')
| -rw-r--r-- | tor-spec.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tor-spec.txt b/tor-spec.txt index f728478..2116097 100644 --- a/tor-spec.txt +++ b/tor-spec.txt @@ -662,7 +662,7 @@ see tor-design.pdf. 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 if the versions cell is not well-formed (for example, - if it contains an odd number of bytes). + if the payload contains an odd number of bytes). Any VERSIONS cells sent after the first VERSIONS cell MUST be ignored. (To be interpreted correctly, later VERSIONS cells MUST have a CIRCID_LEN |