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

 The high-level question to answer is:

 > Given a string containing a NURL, how does the GBS client know how to
 set up the connection?

 The answer implied by the ticket description is to look at the scheme and
 for "pb" use HTTP over TLS, for "pb+tor" use HTTP over Tor, and for
 "pb+i2p" use HTTP over I2P.

 >  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.

 It sounds like this means there might be an alternate answer possible:

 Look at the scheme.  If it is "pb" and the hostname does not end with
 ".onion" then use HTTP over TLS.  If it is "pb" and the hostname does end
 with ".onion" then use HTTP over Tor.  If it is "pb+i2p" then use HTTP
 over I2P.

 Did I understand the Tor interaction correctly?

 If so, I still might prefer the "pb+tor" scheme because of the symmetry it
 maintains with the other two transports to be supported.

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