[tahoe-dev] Tahoe-LAFS, Tor and Tails

[Kill Your TV]

On Fri,  9 Aug 2013 03:01:30 +0000 (UTC)
Leif Ryge <leif at synthesize.us> wrote:

[snip]

> I believe the current version is fixed, but after making
> that mistake I am a little bit less confident in it. :(

I've not tried the script but after a quick skim it looks OK. 

We have been using tahoe on I2P for a few years but we have to do
things a bit differently due to not having something similiar to
"torify" or "torsocks" as an option. We need to patch the source. (Tahoe
tickets #1007 and #1010 apply, as do foolscap #150 and #151). We also
use a patch from #68 to add multiple introducer support.

A shell script is provided to automate the patched installation. Our
tahoe install script
- fetches tahoe, its deps, and patches from a site hosted within I2P. If
  you already have the necessary files the only fetching is done by the
  tahoe installation process itself via proxies within I2P, see #2055.
  The script sets http_proxy and https_proxy to use 'our' outproxies'
  by default. (Since I also use Tor (don't we all?) I set my https_proxy
  to go out on port 8118.)
- verifies that the sha256 checksums match
- patches tahoe and foolscap to add proxy support
- compiles and 'installs' tahoe to ./tahoe-lafs-i2p

Whenever I test our installation script on PCs/VMs that don't have I2P,
the tahoe installation process doesn't successfully go out to the
internet. The installation looks the same as it does when one is
completely disconnected from the internet.


tl;dr: Your bootstrap script should fine. :)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20130809/1cfb8e55/attachment.pgp>