aboutsummaryrefslogtreecommitdiff
path: root/address-spec.txt
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2011-09-06 20:24:19 -0400
committerRoger Dingledine <arma@torproject.org>2011-09-06 20:24:19 -0400
commit06cf12f86e398318deec2338c1551a0312097f14 (patch)
tree8e876a8d3bc4f1d00797a315a4d5d07006fc108f /address-spec.txt
parent60118160829d7d01b70c04004aa39c4ef62cb089 (diff)
downloadtorspec-06cf12f86e398318deec2338c1551a0312097f14.tar.gz
torspec-06cf12f86e398318deec2338c1551a0312097f14.zip
Resume documenting the dot-noconnect syntax
Just because it's gone from 0.2.2.x doesn't mean we should undocument it. Manually reverts (and modifies) c148e13154b81.
Diffstat (limited to 'address-spec.txt')
-rw-r--r--address-spec.txt13
1 files changed, 13 insertions, 0 deletions
diff --git a/address-spec.txt b/address-spec.txt
index ce6d2b6..2b361d1 100644
--- a/address-spec.txt
+++ b/address-spec.txt
@@ -56,3 +56,16 @@
When Tor sees an address in this format, it tries to look up and connect to
the specified hidden service. See rend-spec.txt for full details.
+4. .noconnect
+
+ SYNTAX: [string].noconnect
+
+ When Tor sees an address in this format, it immediately closes the
+ connection without attaching it to any circuit. This is useful for
+ controllers that want to test whether a given application is indeed
+ using the same instance of Tor that they're controlling.
+
+ This feature was added in Tor 0.1.2.4-alpha, and taken out in Tor
+ 0.2.2.1-alpha over fears that it provided another avenue for detecting
+ Tor users via application-level web tricks.
+