aboutsummaryrefslogtreecommitdiff
path: root/tor-spec.txt
AgeCommit message (Collapse)Author
2021-05-27Document behavior on multiple TLS-over-TCP linkspecsNick Mathewson
2021-05-13Document current circid selection behaviorNick Mathewson
2021-03-03Describe handling of END cells and half-open streams.Nick Mathewson
Originally designed in tor#25573 as part of a defense for the DropMark attack by Rochet and Pereira. Closes torspec#33.
2020-09-17Describe the actual RELAY cell padding algorithm that we use.Nick Mathewson
For indistinguishability, other implementations should pad the same way that we do.
2020-09-17tor-spec: describe the order in which we put link specifiers.Nick Mathewson
Right now, tor encodes them in a certain order; specifying that order can help other implementations be indistinguishable.
2020-09-17tor-spec: describe END cell format better.Nick Mathewson
2020-07-06Document relay commands for circpad cells.Mike Perry
2020-06-26Add a sentence about how the digest is calculated; closes tor#32830Nick Mathewson
2020-06-24Remove a very obsolete note about compatibility notesNick Mathewson
2020-06-17Rename a circuit end reason.Nick Mathewson
OR_CONN_CLOSED has been CHANNEL_CLOSED since 0.2.4.4-alpha.
2020-05-18tor-spec: Add Relay=3 protocol versionteor
With minor edits from the draft in proposal 311. Closes ticket 33227.
2020-04-28tor-spec: Do the same extend checks as torteor
Update the extend checks to match tor's implementation, particularly the comments in channel_tls_matches_target_method().
2020-04-28tor-spec: Explain the truncated reason betterteor
It's the payload of a DESTROY cell, but the data of a RELAY_TRUNCATED cell.
2020-04-28tor-spec: Extends accept all-zero ed25519 keysteor
The spec gives conficting advice about all-zero ed25519 keys in extends. Resolve this conflict by documenting tor's current behaviour. Also move a sentence about circuit IDs, so it's closer to the associated paragraph.
2019-12-10convert text blocks into widely compatible "blockquote" syntaxHans-Christoph Steiner
This only adds newline characters to make the existing text blocks act like "blockquote" or "code block" syntax in Markdown, asciidoc, and others. This was accomplished by manually reviewing the output of this script: ```bash for f in *.txt; do cat $f | python -c "import sys,re;print(re.sub(r'(\n {0,3}[^ \n][^\n]*\n)( {4,}[^\n]*)', r'\1\n\2', sys.stdin.read()))" > ${f}.tmp mv ${f}.tmp $f done ```
2019-12-02Merge remote-tracking branch 'dgoulet/ticket32617_01'George Kadianakis
2019-11-26rend-spec-v3.txt: Merge prop305 in itDavid Goulet
Signed-off-by: David Goulet <dgoulet@torproject.org>
2019-11-26fix erroneous header numbering punctuationHans-Christoph Steiner
The clear standard is trailing "." after each numeric section. This fixes the small handful of outliers. This makes it easy to convert these headers to common markup formats, for example: http://hyperpolyglot.org/lightweight-markup
2019-08-190.4.1.5 is scheduled to be a stable release.Nick Mathewson
2019-08-19tor-spec: Clarify protover Padding=1 and Padding=2.George Kadianakis
2019-05-31tor-spec: Add authenticated SENDMEsDavid Goulet
This merges proposal 289 into tor-spec.txt. Most of the circuit-level flow control section has been rewritten to be clearer and better detail version 0 and 1. Closes #30365 Signed-off-by: David Goulet <dgoulet@torproject.org>
2019-01-15Merge remote-tracking branch 'asn-github/bug28142'Nick Mathewson
2018-12-21my next surfer band name will be the protocoolsRoger Dingledine
2018-12-20Merge remote-tracking branch 'tor-github/pr/46'Nick Mathewson
2018-12-11Mark proposal 297-safer-protocol-shutdowns.txt as implemented (#27735)Nick Mathewson
2018-12-06Update syntax that describes NETINFO cellrl1987
2018-12-06Specify protover support for circuit-level padding.George Kadianakis
2018-11-29Reword address format definition in section 4.5rl1987
Let's refrain from mentioning section 6.4 in here, as the format is not exactly the same - not all address type field values from section 6.4 make sense in NETINFO cell and NETINFO cell does not have a TTL value at the end of each address. It's a little confusing to suggest that there is a reuse of wire format fragment between RELAY_RESOLVED and NETINFO cells.
2018-08-08Merge remote-tracking branch 'teor/ticket26885'Nick Mathewson
2018-07-30Clarify some places where we meant RELAY to include RELAY_EARLY.Nick Mathewson
2018-07-30Merge branch '26228-padding-bytes_squashed'Nick Mathewson
2018-07-30tor-spec: Prop#289: RELAY cell padding should be randomisedteor
Updates tor-spec for 26871
2018-07-30tor-spec: Clarify padding bytes in VPADDING, PADDING, and DROP cellsteor
Closes 26870.
2018-07-26tor-spec: Generalise "exit" to "end" where appropriateteor
Closes #26885.
2018-07-26tor-spec: Generalise the first-hop ban to rend points and exit streamsteor
Part of 26885.
2018-07-20Clarify all-zeroes relay fingerprint behaviorTaylor Yu
The all-zeroes special case for EXTEND/EXTEND2 cells is for relay fingerprints/public keys, not cell crypto digests. Closes ticket 26893.
2018-07-20Say CREATE/CREATE2, etc. where neededTaylor Yu
Not all of the text describing CREATE, CREATED, EXTEND, or EXTENDED cells was updated when the "2"-suffixed versions were added. Closes ticket 26894.
2018-07-20Merge branch '26860-decryption-order-squashed'Nick Mathewson
2018-07-20tor-spec: circIDs are no longer chosen based on nicknamesteor
And perhaps they never were?
2018-07-20tor-spec: fix some section numbersteor
2018-07-20tor-spec: Specify how EXTEND2 cells are turned into CREATE2 cellsteor
Also generalised the EXTENDED to CREATED section so it covers EXTENDED2 to CREATED2. Closes 26859.
2018-07-19tor-spec: Rewrite the Routing Relay Cells sectionteor
The section now consists of: * forward encryption at the client * forward decryption at ORs * backward encryption at the end (exit) * backward decryption at the client Part of 26860.
2018-07-19tor-spec: Fix recognized error, and explain why the field existsteor
Closes 26872.
2018-07-18Update spec with SHOULD/MUST behavior for padding bytesDave Rolek
In doing so, specify a general behavior for padding bytes in Section 3 and cross-reference other locations to this, to aid in future consistency. Also clarify a few vague parts of the prior wording. Fixes #26860.
2018-07-18Update spec to match correct decryption orderDave Rolek
Fixes #26860.
2018-03-27Fix typo in tor-spec.txtTaylor Yu
Section 5.1.2 erroneously suggested that a client might send an EXTENDED2 cell, which was probably a typo. Also change "a" to "an".
2018-02-13Small tweaks to clarify recognized even moreNick Mathewson
2018-02-08Change clause about recognized to 'may'Damian Johnson
Good point from Roger and Tim on... https://trac.torproject.org/projects/tor/ticket/25171
2018-02-07Clarify what the RELAY cell's 'recognized' field is forDamian Johnson
Our tor-spec left me pretty mystified what the 'recognized' field actually was. It discussed what to do when it was zero, but not what the field *was* or what non-zero meant. Thankfully Roger filled me in over tasty, tasty pizza.
2018-01-12Merge commit '8692de910d'Nick Mathewson
7apu2bq3rhoylwmucxizk54afw5jyda7pho4j5zdcqpwkufke7zdzwad.onion