[tahoe-dev] [tahoe-lafs] #517: make tahoe Tor-friendly

tahoe-lafs trac at allmydata.org
Fri Mar 5 08:26:21 UTC 2010


#517: make tahoe Tor-friendly
------------------------------+---------------------------------------------
 Reporter:  warner            |           Owner:           
     Type:  enhancement       |          Status:  new      
 Priority:  minor             |       Milestone:  undecided
Component:  code-network      |         Version:  1.2.0    
 Keywords:  tor easy privacy  |   Launchpad_bug:           
------------------------------+---------------------------------------------

Comment(by ioerror):

 It seems like we have a few possible interesting use cases:

  1. Tahoe as a client to any grid where all connections leave the Tor
 network
  2. Tahoe storage nodes that advertise their address as their respective
 .onion address
   a. All outgoing TCP connections from the storage node must only connect
 through Tor
   a. The storage node should not leak it's own known IP
  3. A full Tahoe grid that is only available over Tor
   a. The introducer should reject listing all peers that aren't .onions
   a. All nodes should be reachable as .onions (thus we solve the NAT
 problem)
   a. It's super slow and everyone loves the idea but the practice is full
 of shame

 I think that 1 is currently possible with tsocks and a functional Tor
 client. 2 seems to be easy enough to do with the tub.location patch and
 iptables wizardry. 3 seems likely best solved with transparent Tor
 proxying and manual tub.location stuffing.

 As a side note, it's probably the case that Tahoe should weight
 reconstruction and not use blocks from .onions as their first choice for
 streaming data.

 Is there anything else that's missing? What other ways should we use Tor
 and Tahoe together?

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/517#comment:8>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid


More information about the tahoe-dev mailing list