[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3888: Handling Tor and i2p in NURLs

[Tahoe-LAFS]

#3888: Handling Tor and i2p in NURLs
--------------------------+-----------------------------------
     Reporter:  itamarst  |      Owner:
         Type:  defect    |     Status:  new
     Priority:  normal    |  Milestone:  HTTP Storage Protocol
    Component:  unknown   |    Version:  n/a
   Resolution:            |   Keywords:
Launchpad Bug:            |
--------------------------+-----------------------------------

Comment (by meejah):

 I'm not sure that there's a problem with Tor here; onion services are on
 syntactically-valid `.onion` URLs with a well-known TLD of ".onion" (RFC
 7686) which are "just" host-names.

 Of course, you do need something that understands what to do with those
 (which in practice means "using SOCKS5 to the local Tor daemon"). For our
 case here, txtorcon understands all this and provides
 "IStreamClientEndpoint" or "IAgent" type interfaces.

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