aboutsummaryrefslogtreecommitdiff
path: root/spec/tor-spec
diff options
context:
space:
mode:
authorAlexander Færøy <ahf@torproject.org>2024-01-22 19:35:39 +0000
committerAlexander Færøy <ahf@torproject.org>2024-01-22 19:35:39 +0000
commit693947be7be58e45d0c54495d58315cca7c24db5 (patch)
treea39505ee1b5c4a0a8e6362e37f438d3730710de2 /spec/tor-spec
parent18c77a790fdc3c6914fd5494f17d8b702526b560 (diff)
parent67345c27c293793758967ee36239bad3bc05612c (diff)
downloadtorspec-693947be7be58e45d0c54495d58315cca7c24db5.tar.gz
torspec-693947be7be58e45d0c54495d58315cca7c24db5.zip
Merge branch 'rend_connected_empty' into 'main'
Misc clarifications around CONNECTED and BEGIN behavior See merge request tpo/core/torspec!237
Diffstat (limited to 'spec/tor-spec')
-rw-r--r--spec/tor-spec/opening-streams.md12
1 files changed, 12 insertions, 0 deletions
diff --git a/spec/tor-spec/opening-streams.md b/spec/tor-spec/opening-streams.md
index 757f776..799b4dc 100644
--- a/spec/tor-spec/opening-streams.md
+++ b/spec/tor-spec/opening-streams.md
@@ -68,6 +68,18 @@ payload is in one of the following formats:
A number of seconds (TTL) for which the address may be cached [4 octets]
```
+Implementations MUST accept either of these formats,
+and MUST also accept an empty RELAY_CONNECTED message body.
+
+Implmentations MAY ignore the address value,
+and MAY choose not to cache it.
+If an implementation chooses to cache the address,
+it SHOULD NOT reuse that address with any other circuit.
+
+> The reason not to cache an address
+> is that the exit might have lied about the actual address of the host,
+> or might have given us a unique address to identify us in the future.
+
\[Tor exit nodes before 0.1.2.0 set the TTL field to a fixed value. Later
versions set the TTL to the last value seen from a DNS server, and expire
their own cached entries after a fixed interval. This prevents certain