Age | Commit message (Collapse) | Author | |
---|---|---|---|
2018-07-20 | tor-spec: Specify how EXTEND2 cells are turned into CREATE2 cells | teor | |
Also generalised the EXTENDED to CREATED section so it covers EXTENDED2 to CREATED2. Closes 26859. | |||
2018-07-19 | tor-spec: Rewrite the Routing Relay Cells section | teor | |
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-19 | tor-spec: Fix recognized error, and explain why the field exists | teor | |
Closes 26872. | |||
2018-07-18 | Update spec with SHOULD/MUST behavior for padding bytes | Dave 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-18 | Update spec to match correct decryption order | Dave Rolek | |
Fixes #26860. | |||
2018-03-27 | Fix typo in tor-spec.txt | Taylor 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-13 | Small tweaks to clarify recognized even more | Nick Mathewson | |
2018-02-08 | Change clause about recognized to 'may' | Damian Johnson | |
Good point from Roger and Tim on... https://trac.torproject.org/projects/tor/ticket/25171 | |||
2018-02-07 | Clarify what the RELAY cell's 'recognized' field is for | Damian 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-12 | Merge commit '8692de910d' | Nick Mathewson | |
2017-09-20 | Document Ed25519 link authentication and EXTEND formats. | Nick Mathewson | |
2017-09-20 | Remove a comment about unimplemented feature in 0.2.0.23-rc | Nick Mathewson | |
2017-09-20 | VERSIONS cells sent after the initial VERSIONS cell are dropped | teor | |
Resolves 22931. | |||
2017-09-20 | When VPADDING cells are sent early, specify their CIRC_ID_LEN | teor | |
Resolves 22929. | |||
2017-09-19 | Clarify which ciphers we are talking about in tor-spec 0.3. | Nick Mathewson | |
Make sure we mention all the ciphers we use, and use the phrase "unless otherwise specified" liberally to make sure that people don't think that we're still RSA1024 all over. Also rename the hybrid encryption thing to "legacy hybrid encryption", and put it in its own section. Closes ticket 22722. | |||
2017-09-19 | clarify that RELAY_SENDME cells are empty | Nick Mathewson | |
2017-09-19 | Document exact contents of RELAY_RESOLVED cells | Nick Mathewson | |
We had been vague about what the Value fields here were. Also, document that addresses in NETINFO don't have TTLs. Closes ticket 22937. | |||
2017-09-19 | Correct our description of circID MSB logic | Nick Mathewson | |
In protocol <= 3 we allowed OPs to set the circID msb however they wanted. We don't do that any more in >= 4. Closes ticket 22882. | |||
2017-09-07 | Describe actual use of NETINFO fields | Nick Mathewson | |
Instead of saying the clock skew and "your address" fields are unused, describe the dangers of using them as unconditionally trusted. | |||
2017-09-07 | Mention link protocol 5 in section 9.1 | Nick Mathewson | |
Closes ticket 22918. | |||
2017-09-06 | Correct description of which cells are allowed during the handshake | Nick Mathewson | |
We said that PADDING was allowed, but it wasn't. Bug 22934. | |||
2017-08-23 | 14312: Clarify the status of extra bytes in RELAY_END payload. | Nick Mathewson | |
2017-08-21 | Clarify response to RELAY_BEGIN_DIR; fixes 23276 | Nick Mathewson | |
2017-07-25 | may->must, and split a sentence into two | Nick Mathewson | |
The original was incorrect to say "You may do A if B, C otherwise." but it seems less clear to say "You MUST do A if B, C otherwise." than it is to say "If A, you MUST B. If not A, you MUST C." Closes ticket 22951 | |||
2017-07-24 | Clarify the TAP hybrid encryption scheme | Nick Mathewson | |
This is only used in TAP and old-style hidden services, and it's half malleable. I've clarified how the code behaves by adding the change suggested in #22987. I've also noted: I've also noted that we don't actually reach case 1 with any usage of this algorithm. I've also replaced Roger's note that someday we'll add a MAC with an admonition not to use this hybrid encryption approach for anything new. We're not planning to add a MAC; we've migrated to ntor instead. | |||
2017-07-24 | Add a note on (not) using TLS compression. | Nick Mathewson | |
2017-07-24 | Clarify how clients find the expected identity key | Nick Mathewson | |
Fixes bug 22862; based on patch from Teor. | |||
2017-05-16 | Merge prop274; mark it closed. | Nick Mathewson | |
2017-05-15 | Merge branch 'prop140_completed_squashed' | Nick Mathewson | |
2017-05-15 | Merge prop140 into dir-spec.txt | Nick Mathewson | |
2017-05-14 | resolve a confusing typo about the v3 link handshake | Roger Dingledine | |
unless it was meant to be this way, and I'm the one who got confused? | |||
2017-05-10 | Correct recommended/required protocols list per 21109 | Nick Mathewson | |
2017-05-08 | Merge remote-tracking branch 'mikeperry/padding_spec' | Nick Mathewson | |
2017-02-15 | protover: Add new version for prop224 for HSIntro/HSDir | David Goulet | |
Signed-off-by: David Goulet <dgoulet@torproject.org> | |||
2017-01-18 | add explanation of KEYID(A) function | Kacper Kołodziej | |
based on proposal #216, where KEYID(A) = A | |||
2016-12-18 | clarify how to count sendme windows | Roger Dingledine | |
2016-12-18 | remove extraneous word | Roger Dingledine | |
2016-11-29 | Merge proposal 264 to dir-spec and tor-spec | David Goulet | |
Signed-off-by: David Goulet <dgoulet@torproject.org> | |||
2016-09-05 | Remove 3DES as a required suite; add the minimal AES one. | Nick Mathewson | |
2016-01-27 | At long last, a padding specification appears. | Mike Perry | |
Baby steps. Crawl before you can walk. Walk before you can run. | |||
2016-01-14 | In addition to the content, explain the format too | Sven Herzberg | |
The term “X509 certificate” actually only describes one part of the format. Be more explicit to mean DER encoded certificates (in contrast to PEM encoded certifcates). | |||
2015-08-12 | Start writing/copying/adding a bunch of stuff about ed25519 keys | Nick Mathewson | |
2015-06-29 | Fix a misspelling in tor-spec.txt | teor | |
Patch by Tim Wilson-Brown ("teor"). | |||
2015-02-03 | three typo fixes | Roger Dingledine | |
2015-01-06 | Fix an error in the description of KDF-RFC5869 | Tom van der Woerdt | |
2015-01-06 | MSBs are actually the other way around | Tom van der Woerdt | |
2015-01-04 | Document the OOM algorithm in tor-spec. (#13794) | Nick Mathewson | |
2014-08-02 | update the spec to say that you must refuse inbound relay_early cells | Roger Dingledine | |
2014-06-01 | fix a repeated-typo; spotted by Yawning | Nick Mathewson | |
2014-05-14 | Fix minor typos in tor-spec.txt | Martin Kepplinger | |