Opened at 2010-03-27T21:03:28Z
Last modified at 2021-03-30T18:40:19Z
#1007 new enhancement
HTTP proxy support for node to node communication — at Initial Version
| Reported by: | duck | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | soon |
| Component: | code-network | Version: | 1.6.1 |
| Keywords: | privacy anonymity firewall foolscap anti-censorship i2p | Cc: | warner, killyourtv@…, skydrome@… |
| Launchpad Bug: |
Description
To use Tahoe-LAFS over the 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)
HTTP Proxy support to Foolscap