aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJacob Appelbaum <jacob@appelbaum.net>2011-02-18 16:03:31 -0500
committerNick Mathewson <nickm@torproject.org>2011-02-18 16:03:31 -0500
commit38224f95a690c445e52d6f11180727e8c728999d (patch)
tree790121c2430ae751d447d3d44bcea14674dc518c /doc
parentc1c8f51d77fef58f6015250acad5ee8c51d6aa10 (diff)
downloadtor-38224f95a690c445e52d6f11180727e8c728999d.tar.gz
tor-38224f95a690c445e52d6f11180727e8c728999d.zip
Quick patch to pluggable transport spec
Diffstat (limited to 'doc')
-rw-r--r--doc/spec/proposals/ideas/xxx-pluggable-transport.txt4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/spec/proposals/ideas/xxx-pluggable-transport.txt b/doc/spec/proposals/ideas/xxx-pluggable-transport.txt
index 2507f52749..53ba9c630b 100644
--- a/doc/spec/proposals/ideas/xxx-pluggable-transport.txt
+++ b/doc/spec/proposals/ideas/xxx-pluggable-transport.txt
@@ -126,7 +126,9 @@ Design overview
To configure one of these programs, it should be sufficient simply to
list it in your torrc. The program tells Tor which transports it
- provides.
+ provides. The Tor consensus should carry a new approved version number that
+ is specific for pluggable transport; this will allow Tor to know when a
+ particular transport is known to be unsafe safe or non-functional.
Bridges (and maybe relays) report in their descriptors which transport
protocols they support. This information can be copied into bridge