aboutsummaryrefslogtreecommitdiff
path: root/proposals/180-pluggable-transport.txt
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2011-04-11 19:27:43 -0400
committerRoger Dingledine <arma@torproject.org>2011-04-11 19:27:43 -0400
commite65b0219700ab09819aebeab6034df9cbb3b3591 (patch)
tree6f29023b912b978f2d60a296dc2ff3de628de00a /proposals/180-pluggable-transport.txt
parent648ca5d78889a440fac1594f89fc3cab15dbb6a3 (diff)
downloadtorspec-e65b0219700ab09819aebeab6034df9cbb3b3591.tar.gz
torspec-e65b0219700ab09819aebeab6034df9cbb3b3591.zip
make explicit how to distinguish old bridge lines
Diffstat (limited to 'proposals/180-pluggable-transport.txt')
-rw-r--r--proposals/180-pluggable-transport.txt9
1 files changed, 9 insertions, 0 deletions
diff --git a/proposals/180-pluggable-transport.txt b/proposals/180-pluggable-transport.txt
index daa81bf..5e9e5b1 100644
--- a/proposals/180-pluggable-transport.txt
+++ b/proposals/180-pluggable-transport.txt
@@ -159,6 +159,15 @@ Specifications: Client behavior
The "id-fingerprint" field is always provided in a field named
"keyid", if it was given. Method names must be C identifiers.
+ For reference, the old bridge format was
+ bridge address[:port] [id-fingerprint]
+ where port defaults to 443 and the id-fingerprint is optional. The
+ new format can be distinguished from the old one by checking if the
+ first argument has any non-C-identifier characters. (Looking for a
+ period should be a simple way.) Also, while the id-fingerprint could
+ optionally include whitespace in the old format, whitespace in the
+ id-fingerprint is not permitted in the new format.
+
Example: if the bridge line is "bridge trebuchet www.example.com:3333
rocks=20 height=5.6m" AND if the Tor client knows that the
'trebuchet' method is provided by a SOCKS5 proxy on