aboutsummaryrefslogtreecommitdiff
path: root/proposals/224-rend-spec-ng.txt
diff options
context:
space:
mode:
authorJohn Brooks <special@torproject.org>2016-05-10 14:25:21 -0400
committerGeorge Kadianakis <desnacked@riseup.net>2016-05-12 14:24:03 -0400
commitf9313163c3f85d7bbb92f90947dfe9021f637c89 (patch)
treedc1d89b6e83323716197e44b34ff97e98b9d0224 /proposals/224-rend-spec-ng.txt
parente896dcf2f1e2782c5ba7dc72bdccc39b7f519af1 (diff)
downloadtorspec-f9313163c3f85d7bbb92f90947dfe9021f637c89.tar.gz
torspec-f9313163c3f85d7bbb92f90947dfe9021f637c89.zip
prop224: More trivial fixups.
- Sectioning fixes
Diffstat (limited to 'proposals/224-rend-spec-ng.txt')
-rw-r--r--proposals/224-rend-spec-ng.txt12
1 files changed, 4 insertions, 8 deletions
diff --git a/proposals/224-rend-spec-ng.txt b/proposals/224-rend-spec-ng.txt
index 292ab3f..5db0ae3 100644
--- a/proposals/224-rend-spec-ng.txt
+++ b/proposals/224-rend-spec-ng.txt
@@ -1165,12 +1165,9 @@ Table of contents:
earlier fields.
Older versions of Tor always use a 1024-bit RSA key for these introduction
- authentication keys. Newer hidden services MAY use RSA keys up 1904
- bits. Any more than that will not fit in a RELAY cell payload.
+ authentication keys.
-[There is no 3.1.3?]
-
-3.1.4. Acknowledging establishment of introduction point [INTRO_ESTABLISHED]
+3.1.3. Acknowledging establishment of introduction point [INTRO_ESTABLISHED]
After setting up an introduction circuit, the introduction point reports its
status back to the hidden service host with an INTRO_ESTABLISHED cell.
@@ -1183,9 +1180,8 @@ Table of contents:
EXT_FIELD_LEN [1 byte]
EXT_FIELD [EXT_FIELD_LEN bytes]
- [Worth mentioning that old-school Tor relays send back an empty
- payload here? Or, even better, not mentioning it if we simplify
- 3.1.2 to "don't do that". -RD]
+ Older versions of Tor send back an empty INTRO_ESTABLISHED cell instead.
+ Services must accept an empty INTRO_ESTABLISHED cell from a legacy relay.
3.2. Sending an INTRODUCE1 cell to the introduction point. [SEND_INTRO1]