[tahoe-lafs-trac-stream] [Tahoe-LAFS] #867: use ipv6

[Tahoe-LAFS]

#867: use ipv6
-------------------------+-------------------------------------------------
     Reporter:  warner   |      Owner:  ClashTheBunny
         Type:           |     Status:  assigned
  enhancement            |
     Priority:  major    |  Milestone:  undecided
    Component:  code-    |    Version:  1.5.0
  network                |   Keywords:  ipv6 firewall twisted foolscap
   Resolution:           |  test-needed
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by lpirl):

 Replying to [comment:36 warner]:
 > Good points. Twisted's endpoint language uses `tcp:` for IPv4-based TCP
 ports, and `tcp6:` for IPv6-based ones.. they didn't add a `tcp4:` for
 anything, which is a bit inconsistent, I guess. I kind of like the idea of
 redefining `tub.port=`'s `tcp:` to mean both, but I wonder if it'd be
 confusing, since then we can no longer claim it's exactly an Endpoint
 string.

 I see, interesting. I can't judge on this. 0.02:
 Does it actually matter to have proper Endpoints (as a user: never cared)?
 Do Tahoe users ever come in direct contact with Twisted (as a user: don't
 want to)?
 But your point is definitely to consider and maybe a show stopper for
 `tcp4:`.

 > Oh also, maybe we should only do the dual-`tcp:`+`tcp6:` thing when
 we're automatically setting up the listener (with `tahoe create-node
 --hostname=ABC`). In other cases, let the user be explicit (which might
 mean that the `--port=` argument to `tahoe create-node` needs to accept
 multiple ports too.. maybe `tahoe create-node --port "tcp:1234 tcp6:1234"`
 ?).

 Yes, IMHO the automatic mode should always be default unless explicitly
 configured otherwise.
 `tahoe create-node --port …` could use the same delimiter as `tub.port`
 for consistency.

 > Also also, endpoint strings can include paths (to TLS certificates, and
 unix-domain sockets), and on a sufficiently ill-advised system, those
 might include spaces. So maybe whitespace as a delimiter isn't such a
 great idea after all.

 Speaking of file system paths (mind Windows), there are not much
 delimiters we can use while maintaining full compatibility with all
 possible paths. It's probably inevitable to choose "just any".

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