aboutsummaryrefslogtreecommitdiff
path: root/spec/rend-spec
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2023-12-07 16:13:51 -0500
committerNick Mathewson <nickm@torproject.org>2023-12-07 16:13:51 -0500
commit67345c27c293793758967ee36239bad3bc05612c (patch)
tree90daffbade1a5ac83e05b51154b03cfc83751b49 /spec/rend-spec
parent61945e4acdf872a392f8c24b13b40617cbf1a5fd (diff)
downloadtorspec-67345c27c293793758967ee36239bad3bc05612c.tar.gz
torspec-67345c27c293793758967ee36239bad3bc05612c.zip
rend-spec: Clarify CONNECTED contents
Diffstat (limited to 'spec/rend-spec')
-rw-r--r--spec/rend-spec/managing-streams.md6
1 files changed, 4 insertions, 2 deletions
diff --git a/spec/rend-spec/managing-streams.md b/spec/rend-spec/managing-streams.md
index a32a352..9eb1e82 100644
--- a/spec/rend-spec/managing-streams.md
+++ b/spec/rend-spec/managing-streams.md
@@ -25,7 +25,9 @@ address and flags.
If a service chooses to reject a BEGIN message, it should typically
destroy the circuit entirely to prevent port scanning,
resource exhaustion, and other undesirable behaviors.
-If it does not, it should send back an `END` message with the `DONE` reason,
+But if it rejects the BEGIN without destroy the circuit,
+it should send back an `END` message with the `DONE` reason,
to avoid leaking any further information.
-
+If the service chooses to accept the BEGIN message,
+it should send back a CONNECTED message with an empty body.