[tahoe-lafs-trac-stream] [tahoe-lafs] #1007: HTTP proxy support for node to node communication

[tahoe-lafs]

#1007: HTTP proxy support for node to node communication
-------------------------+-------------------------------------------------
     Reporter:  duck     |      Owner:  davidsarah
         Type:           |     Status:  new
  enhancement            |  Milestone:  soon
     Priority:  minor    |    Version:  1.6.1
    Component:  code-    |   Keywords:  privacy anonymity firewall foolscap
  network                |  anti-censorship
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Old description:

> To use Tahoe-LAFS over the [http://www.i2p2.de/ I2P anonymous network] I
> have added HTTP proxy support to the Foolscap library. Most of the work
> is in Foolscap, but within Tahoe it must also be possible to enable this
> functionality and specify which HTTP proxy to use. All I2P nodes have
> this HTTP proxy enabled by default on `127.0.0.1:4444`.
>
> For the anonymous network use case, every connection to storage nodes and
> introducers will have to be through the anonymous network; it is not
> acceptable to mix anonymous and non-anonymous connections. The intention
> is to provide anonymity to both clients and node operators.
>
> A reference implementation is available on http://duck.i2p.to/tahoe-lafs/
> , as of today (2010-03-27) a test grid is operating inside I2P with 21
> nodes, of which 6 storage nodes and 1 introducer.
>
> Example of configuration in `tahoe.cfg`:
> {{{
>     [node]
>     ...
>     http_proxy = 127.0.0.1:4444
> }}}
>
> Snippit showing how this is used in `node.py`:
> {{{
>     http_proxy = self.get_config("node", "http_proxy", "")
>     if http_proxy:
>         self.tub.setOption("httpProxy", http_proxy)
> }}}

New description:

 To use Tahoe-LAFS over the [http://www.i2p2.de/ I2P anonymous network] I
 have added HTTP proxy support to the Foolscap library. Most of the work is
 in Foolscap, but within Tahoe it must also be possible to enable this
 functionality and specify which HTTP proxy to use. All I2P nodes have this
 HTTP proxy enabled by default on `127.0.0.1:4444`.

 For the anonymous network use case, every connection to storage nodes and
 introducers will have to be through the anonymous network; it is not
 acceptable to mix anonymous and non-anonymous connections. The intention
 is to provide anonymity to both clients and node operators.

 A reference implementation is available on http://duck.i2p.to/tahoe-lafs/
 , as of today (2010-03-27) a test grid is operating inside I2P with 21
 nodes, of which 6 storage nodes and 1 introducer.

 Example of configuration in `tahoe.cfg`:
 {{{
     [node]
     ...
     http_proxy = 127.0.0.1:4444
 }}}

 Snippit showing how this is used in `node.py`:
 {{{
     http_proxy = self.get_config("node", "http_proxy", "")
     if http_proxy:
         self.tub.setOption("httpProxy", http_proxy)
 }}}

--

Comment (by killyourtv):

 Attached is an updated patch (0001-outbound-proxy-support.patch​ ) that
 changes the config option to outbound-proxy. The patch applies cleanly to
 current trunk.

 (I'm still trying to learn Python so please forgive any n00b errors. I
 also need to learn how to write unit tests).

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1007#comment:24>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage