id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	launchpad_bug
1007	HTTP proxy support for node to node communication	duck	davidsarah	"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)
}}}"	enhancement	new	minor	soon	code-network	1.6.1		privacy anonymity firewall foolscap anti-censorship	warner