aboutsummaryrefslogtreecommitdiff
path: root/pt-spec.txt
diff options
context:
space:
mode:
authorGeorge Kadianakis <desnacked@riseup.net>2012-10-30 03:30:39 +0200
committerNick Mathewson <nickm@torproject.org>2012-11-06 17:56:08 -0500
commit34d5711829cac4611c0ce43157843b572d63fe86 (patch)
tree2349aa08d2c11779be5c485f8c77b34e865e515c /pt-spec.txt
parent580ce9f083e5dec1c9b3aa49ef2e76ed30908b39 (diff)
downloadtorspec-34d5711829cac4611c0ce43157843b572d63fe86.tar.gz
torspec-34d5711829cac4611c0ce43157843b572d63fe86.zip
Be able to specify the bind address of managed proxies.
Diffstat (limited to 'pt-spec.txt')
-rw-r--r--pt-spec.txt14
1 files changed, 14 insertions, 0 deletions
diff --git a/pt-spec.txt b/pt-spec.txt
index ffabb4d..0da004a 100644
--- a/pt-spec.txt
+++ b/pt-spec.txt
@@ -134,6 +134,20 @@ Server behavior
then Tor will launch the megaproxy binary twice: once with the option
--foo and once with the option --bar.
+ The address that a managed proxy will use to bind can be configured with:
+ ServerTransportListenAddr <method> <address:port>
+
+ For example, a valid configuration would be:
+ ServerTransportPlugin obfs2,obfs3,stegotorus exec /usr/bin/obfsproxy --managed
+ ServerTransportListenAddr obfs2 0.0.0.0:4200
+ ServerTransportListenAddr stegotorus 98.23.4.45:6559
+
+ If no ServerTransportListenAddr is specified and it's the first time
+ that Tor encounters that transport, Tor will instruct the managed
+ proxy to bind to a random TCP port on 0.0.0.0. If Tor has seen the
+ trasport before, it will instruct the managed proxy to bind to the
+ same TCP port that the transport used last time.
+
Managed proxy interface
When the Tor client or relay launches a managed proxy, it communicates