This is an automated email from the git hooks/post-receive script.
dgoulet pushed a change to branch main in repository torspec.
from 3727309 prop329: Remove unused section and use relay command 19..22 new e66dd71 Clarify that SRV is 256 bits. new c99151c Clarify that revision counter needs to support 64-bit values. new 7116c9c rend-spec-v3: mark some sections as obsolete
The 3 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference.
Summary of changes: dir-spec.txt | 10 ++++++---- rend-spec-v3.txt | 15 +++++++++++++++ 2 files changed, 21 insertions(+), 4 deletions(-)
This is an automated email from the git hooks/post-receive script.
dgoulet pushed a commit to branch main in repository torspec.
commit e66dd71facedd63bbd5e82fd440249afc358295c Author: Nick Mathewson nickm@torproject.org AuthorDate: Tue Dec 20 12:49:25 2022 -0500
Clarify that SRV is 256 bits. --- dir-spec.txt | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/dir-spec.txt b/dir-spec.txt index d2f6c4e..ee36100 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -2115,8 +2115,9 @@ Table of Contents this value, and see section [CONS] for why we include old shared random values in votes and consensus.
- Value is the actual shared random value encoded in base64. NumReveals - is the number of commits used to generate this SRV. + Value is the actual shared random value encoded in base64. It will + be exactly 256 bits long. NumReveals is the number of commits used + to generate this SRV.
"shared-rand-current-value" SP NumReveals SP Value NL
@@ -2133,8 +2134,9 @@ Table of Contents See section [SRCALC] of srv-spec.txt for instructions on how to compute this value given the active commits.
- Value is the actual shared random value encoded in base64. NumReveals - is the number of commits used to generate this SRV. + Value is the actual shared random value encoded in base64. It will + be exactly 256 bits long. NumReveals is the number of commits used to + generate this SRV.
"bandwidth-file-headers" SP KeyValues NL
This is an automated email from the git hooks/post-receive script.
dgoulet pushed a commit to branch main in repository torspec.
commit c99151cc070747b86dca610ddd27d5aa753f2d52 Author: Nick Mathewson nickm@torproject.org AuthorDate: Tue Dec 20 12:50:28 2022 -0500
Clarify that revision counter needs to support 64-bit values. --- rend-spec-v3.txt | 3 +++ 1 file changed, 3 insertions(+)
diff --git a/rend-spec-v3.txt b/rend-spec-v3.txt index fac1395..38a1555 100644 --- a/rend-spec-v3.txt +++ b/rend-spec-v3.txt @@ -1100,6 +1100,9 @@ Table of contents: prevents an attacker from replacing a newer descriptor signed by a given key with a copy of an older version.)
+ Implementations MUST be able to parse 64-bit values for these + counters. + "superencrypted" NL encrypted-string
[Exactly once.]
This is an automated email from the git hooks/post-receive script.
dgoulet pushed a commit to branch main in repository torspec.
commit 7116c9cdaba248aae07a3f1d0e15d9dd102f62c5 Author: Nick Mathewson nickm@torproject.org AuthorDate: Tue Dec 20 12:52:15 2022 -0500
rend-spec-v3: mark some sections as obsolete
All supported versions for relays on the Tor network support v3 onion services. As such, we can mark the sections about "how do I use an 0.2.9.x relay as my intro/rend point?" as obsolete. --- rend-spec-v3.txt | 12 ++++++++++++ 1 file changed, 12 insertions(+)
diff --git a/rend-spec-v3.txt b/rend-spec-v3.txt index 38a1555..0914c81 100644 --- a/rend-spec-v3.txt +++ b/rend-spec-v3.txt @@ -1412,6 +1412,8 @@ Table of contents: "legacy-key" NL key NL
[None or at most once per introduction point] + [This field is obsolete and should never be generated; it + is included for historical reasons only.]
The key is an ASN.1 encoded RSA public key in PEM format used for a legacy introduction point as described in [LEGACY_EST_INTRO]. @@ -1423,6 +1425,8 @@ Table of contents: "legacy-key-cert" NL certificate NL
[None or at most once per introduction point] + [This field is obsolete and should never be generated; it + is included for historical reasons only.]
MUST be present if "legacy-key" is present.
@@ -1656,6 +1660,9 @@ Table of contents: 3.1.2. Registering an introduction point on a legacy Tor node [LEGACY_EST_INTRO]
+ [This section is obsolete and refers to a workaround for now-obsolete Tor + relay versions. It is included for historical reasons.] + Tor nodes should also support an older version of the ESTABLISH_INTRO cell, first documented in rend-spec.txt. New hidden service hosts must use this format when establishing introduction points at older @@ -1696,6 +1703,8 @@ Table of contents:
Older versions of Tor send back an empty INTRO_ESTABLISHED cell instead. Services must accept an empty INTRO_ESTABLISHED cell from a legacy relay. + [The above paragraph is obsolete and refers to a workaround for + now-obsolete Tor relay versions. It is included for historical reasons.]
The same rules for multiplicity, ordering, and handling unknown types apply to the extension fields here as described [EST_INTRO] above. @@ -2136,6 +2145,9 @@ Table of contents:
4.3. Using legacy hosts as rendezvous points
+ [This section is obsolete and refers to a workaround for now-obsolete Tor + relay versions. It is included for historical reasons.] + The behavior of ESTABLISH_RENDEZVOUS is unchanged from older versions of this protocol, except that relays should now ignore unexpected bytes at the end.
tor-commits@lists.torproject.org
-
gitolite role