I abandoned this approach as soon as I realized that I could achieve the same results with a helper.
jody ---- - Think carefully. - Contra mundum - "Against the world" (St. Athanasius) - Credo ut intelliga - "I believe that I may know" (St. Augustin of Hippo) On Thu, Dec 17, 2009 at 5:05 PM, Brian Warner <[email protected]> wrote: > > > 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 > _______________________________________________ > tahoe-dev mailing list > [email protected] > http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev >
_______________________________________________ tahoe-dev mailing list [email protected] http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
