[tahoe-lafs-trac-stream] [tahoe-lafs] #1010: use only 127.0.0.1 as local address

[tahoe-lafs]

#1010: use only 127.0.0.1 as local address
-------------------------+-------------------------------------------------
     Reporter:  duck     |      Owner:  warner
         Type:           |     Status:  new
  enhancement            |  Milestone:  1.9.0
     Priority:  minor    |    Version:  1.6.1
    Component:  code-    |   Keywords:  privacy anonymity test docs anti-
  network                |  censorship reviewed
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by davidsarah):

 Replying to [comment:22 warner]:
 > whoops, I *really* lost track of this one.
 >
 > DS> I meant, what is lost by only having 127.0.0.1 in the list of
 addresses, all the time?
 >
 > Um, if everyone in the grid only publishes 127.0.0.1, then how will
 > distant nodes ever connect to each other? Since we don't have UPnP or
 > NAT traversal, we need everyone (well, N-1) to have+publish a public IP
 > address.

 Yes, I realized that was a silly question (for nodes in general) but
 forgot to unask it. I suppose I was thinking only of clients, or more
 precisely non-servers.

 gdt's suggestion of only including 127.0.0.1 in the list of addresses for
 non-servers makes sense to me, especially given this:

 > Nodes only actually publish their storage FURLs to the Introducer if
 they're configured as servers (see init_storage() in client.py).

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1010#comment:23>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage