[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 daira):

 Replying to [comment:38 warner]:
 > It's because we can get our IP address synchronously, via blocking
 `subprocess.check_output(["ifconfig"])`. We'll do this before Twisted has
 taken over the SIGCHLD handler (which happens in a reactor "during-
 startup" event trigger, so after reactor.run, so after
 `allmydata.node.Node` is constructed).
 >
 > We can also allocate a port synchronously. I just landed some code in
 Foolscap to do this (in `foolscap/util.py`)

 Okay, but aren't these changes independent of the other Tor/I2P changes? I
 don't see how they motivate the potential breakage of backward
 compatibility in making AUTO no longer the default (for non-anonymous
 nodes that listen at all).

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