[tahoe-lafs-trac-stream] [Tahoe-LAFS] #517: make tahoe Tor- and I2P-friendly

[Tahoe-LAFS]

#517: make tahoe Tor- and I2P-friendly
-------------------------+-------------------------------------------------
     Reporter:  warner   |      Owner:  ioerror
         Type:           |     Status:  new
  enhancement            |  Milestone:  undecided
     Priority:  minor    |    Version:  1.2.0
    Component:  code-    |   Keywords:  privacy anonymity anti-censorship
  network                |  i2p tor-protocol usability
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by warner):

 Replying to [comment:36 str4d]:

 > That is how I2P does it ''now'', using duck's HTTP proxy patch. But that
 was only because it was the simplest patch; as I believe was raised in
 that ticket's thread, Tahoe / Foolscap isn't really an HTTP protocol. And
 I2P could just as easily use a SOCKS proxy. But this is only useful for
 clients.

 Ah, great, if I2P can do SOCKS instead, that will make the plugin much
 easier to write. I don't know much about I2P :).

 > This line of discussion raises the question: for this initial client-
 only phase, is the intention to just use plain SOCKS (via `txsocksx`) and
 HTTP (via something like duck's I2P patch) proxies, rather than `txtorcon`
 and `txi2p`?

 I figured that the Foolscap plugin would be implemented by using
 `txsocksx`. For just client connectivity, we don't need full control of
 the Tor/I2P node yet.

 Later, to set up a server, we'll certainly want to use `txtorcon` and
 `txi2p`.

 > > If `[node]anonymous` is true, we'll enforce two things, as per #1010:
 > >
 > > * `[node]tub.location` does not contain "AUTO"
 > > * `[connections]tcp.socks-proxy` is set
 >
 > Should this be "one of `tcp.socks-proxy`, `tor.socks-proxy`, or `i2p
 .sam-api`"?

 It'd need to be `tcp.something`, because that's what will control what
 happens when the Tub connects with a TCP hint. `tor.socks-proxy` controls
 what happens when it connects to a Tor hint, and `i2p.*` will control I2P
 hints. The anonymity safety flag must limit TCP.. it doesn't care so much
 about what happens with hints that have to use a safe connection mode
 anyways.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/517#comment:40>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage