diff options
| author | Nick Mathewson <nickm@torproject.org> | 2023-03-22 14:26:56 -0400 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2023-03-22 14:31:55 -0400 |
| commit | 1aa3a8316a860318cfcdd150eae7904a27bb321f (patch) | |
| tree | 340e3f8a47f3d5a435e9de58b588ef1cfa3d9fb9 /rend-spec-v3.txt | |
| parent | 33308845cec54bfc0096b8ea0339a8ff183aa1b1 (diff) | |
| download | torspec-1aa3a8316a860318cfcdd150eae7904a27bb321f.tar.gz torspec-1aa3a8316a860318cfcdd150eae7904a27bb321f.zip | |
rend-spec: Clarify that linkspec lists should be used verbatim.
This resolved "problem 2" from torspec#193.
Diffstat (limited to 'rend-spec-v3.txt')
| -rw-r--r-- | rend-spec-v3.txt | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/rend-spec-v3.txt b/rend-spec-v3.txt index 757fc1a..d1f7618 100644 --- a/rend-spec-v3.txt +++ b/rend-spec-v3.txt @@ -1398,6 +1398,10 @@ Table of contents: detailed information about the client's version, configuration, or consensus. (See 3.3 for service link specifier handling.) + When connecting to the introduction point, the client SHOULD send + this list of link specifiers verbatim, in the same order as given + here. + "onion-key" SP "ntor" SP key NL [Exactly once per introduction point] @@ -1906,6 +1910,9 @@ Table of contents: the same way as clients do in section 2.5.2.2. In particular, services SHOULD perform basic validity checks on link specifiers, and SHOULD NOT reject unrecognised link specifiers, to avoid information leaks. + The list of link specifiers received here SHOULD either be rejected, or + sent verbatim when extending to the rendezvous point, in the same order + received. The ONION_KEY_TYPE field is: |