[tahoe-dev] tahoe-lafs and socks proxies?

[Brian Warner]

>     As far as I understand, this would be dependent on the Twisted library
>     supporting socks (as a client):
>     <http://twistedmatrix.com/trac/ticket/3508>

For "native" use of a SOCKS proxy, like if you wanted to be able to just
add a line to your tahoe.cfg file and have all network traffic go
through the proxy, then yeah, we'd need support from Twisted that isn't
there yet.

But most SOCKS implementations provide a "runsocks" or "tsocks" launcher
which uses shared-library tricks to cause an unsuspecting program's
socket calls to use the proxy instead of going out direct. Tahoe should
run just fine under one of these. "tsocks tahoe start NODEDIR" instead
of the usual "tahoe start NODEDIR", or possibly "tsocks tahoe run
NODEDIR" if tsocks can't handle the daemonization handoff.

You'd want to look carefully at the address+port that the node deduces
for itself, since they might not be correct, but you can override those
with the tub.location setting in tahoe.cfg . It's similar to the way
that you'd run a Tahoe node behind Tor.

If you get this working, and can write up a basic example, we'd love to
include them in the docs.

cheers,
 -Brian