[tahoe-dev] [tahoe-lafs] #690: raise size limit on furls

[tahoe-lafs]

#690: raise size limit on furls
------------------------------+---------------------------------------------
     Reporter:  adigeo        |       Owner:  warner  
         Type:  defect        |      Status:  assigned
     Priority:  critical      |   Milestone:  1.6.0   
    Component:  code-network  |     Version:  1.4.1   
   Resolution:                |    Keywords:          
Launchpad_bug:                |  
------------------------------+---------------------------------------------
Changes (by warner):

  * status:  new => assigned


Comment:

 I've (slowly, reluctantly) come to agree. The Foolscap DoS-resistance
 approach is impractical. I've created
 [http://foolscap.lothar.com/trac/ticket/127 foolscap#127] to remove it.
 The first step will be to remove the FURL-gift-sizelimit that's causing
 this problem, something I expect to put into foolscap-0.4.2 .

 bewst: I don't see any details about your workaround in this ticket
 (perhaps it is in a different one? or in email?), but I can tell you that
 {{{tub.location}}} is meant to be your externally-visible host+port, to
 which other tahoe nodes can connect (when they want to use your node as a
 storage server). If you don't set {{{tub.location}}}, Tahoe will try to
 enumerate all of your network interfaces and put all of their addresses in
 the location, which is probably why you ran into a FURL-length limitation.

 If your laptop is changing addresses all the time, and you just want to
 discourage other hosts from connecting to you at all (maybe you aren't
 even running a storage server), then set the location to an address that
 won't resolve like "unreachable.example.org:0" or something. Other clients
 will still try and connect to that "location", but they'll get an error
 instead of creating and discarding a bunch of loopback connections. Hm, it
 might be worthwhile to establish a clear syntax for this (like setting
 location to "none" or to an empty string or something).

 source:docs/configuration.txt has an explanation about what
 {{{tub.location}}} does and how it's meant to be used.

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/690#comment:11>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid