[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:  easy privacy anonymity anti-
  network                |  censorship i2p tor
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by dawuud):

 Greetings!

 I have written Tor client and server endpoint parsers...

 Here's the tor client endpoint I wrote... based on txsocksx.
 It has retry logic for guessing the system tor socks port:
 https://github.com/david415/txsocksx/tree/endpoint_parsers_retry_socks

   - should we instead use txtorcon to launch a new tor proc with which
     to speak socks to instead of trying to connect to the system tor
     proc?

   - or maybe if it fails to socks connect to all the tor ports in it's
     list... it fails-back to launching it's own tor proc with txtorcon

 Here's the tor server endpoint I rewrote to launch tor in it's
 `listen` method... so that it remains compatible with Twisted
 IStreamServerEndpoint interface... also I wrote a parser for it :
 https://github.com/david415/txtorcon/tree/endpoint_parser_plugin-rewrite3

   - Meejah and I were discussing the prospect of using the controlPort
     of the system tor proc to create Tor Hidden Services :
 > 10:40 < dawuud> meejah: so your earlier point was that we could use the
 controlPort to configure a hidden service on the system tor?
 > 13:36 < meejah> dawuud: yes, we can use controlPort to configure a new
 hiddenservice in a running system Tor *however*
 > 13:37 < meejah> for how, e.g., it's installed on debian it won't work
 for most people (unless you're running as 'debian-tor' user)
 > 13:37 < meejah> there is a nearly-fixed tor bug adding a "group
 readable" option for hidden-service dirs, and then this will all work fine
 > 13:45 < coderman> oh fuuuu   i'm the worst Tor contrib ever
 https://trac.torproject.org/projects/tor/ticket/11291 meejah ?
 > 14:07 < meejah> coderman: yes, that's the one :)

   - and then the question become *when* to launch tor to create a
     hidden service? I think perhaps as a fallback to first attempting
     to use the system tor controlPort to create the hidden service.

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