[tahoe-lafs-trac-stream] [tahoe-lafs] #1007: HTTP proxy support for node to node communication

tahoe-lafs trac at tahoe-lafs.org
Sun Sep 29 20:22:33 UTC 2013


#1007: HTTP proxy support for node to node communication
-------------------------+-------------------------------------------------
     Reporter:  duck     |      Owner:  davidsarah
         Type:           |     Status:  new
  enhancement            |  Milestone:  soon
     Priority:  minor    |    Version:  1.6.1
    Component:  code-    |   Keywords:  privacy anonymity firewall foolscap
  network                |  anti-censorship
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------
Changes (by zooko):

 * keywords:  privacy anonymity firewall foolscap anti-censorship review-
     needed => privacy anonymity firewall foolscap anti-censorship


Comment:

 Jeff "psi" "ampernand" and I have been looking at this, and we don't think
 HTTP-proxying is the best way to do accomplish this. Because HTTP-proxying
 is meant to provide a request-response style, but Foolscap needs more of a
 "bidirectional byte-stream" style.

 A potentially better way to accomplish it, which we are now poking at, is
 Twisted Endpoints -- see http://foolscap.lothar.com/trac/ticket/203 . One
 potential advantage of that — if it can be made to work — is that it might
 make it easier to support Tor, cjdns, SSL/TLS, IPv6, and maybe other cool
 networking protocols.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1007#comment:28>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage


More information about the tahoe-lafs-trac-stream mailing list