[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-commits] [torspec/master] Be able to specify the bind address of managed proxies.



commit 34d5711829cac4611c0ce43157843b572d63fe86
Author: George Kadianakis <desnacked@xxxxxxxxxx>
Date:   Tue Oct 30 03:30:39 2012 +0200

    Be able to specify the bind address of managed proxies.
---
 pt-spec.txt |   14 ++++++++++++++
 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

_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits