[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2339: Enable specific ports for running tests

[Tahoe-LAFS]

#2339: Enable specific ports for running tests
-----------------------------------------+---------------------------------
     Reporter:  cipherpunks              |      Owner:  daira
         Type:  defect                   |     Status:  closed
     Priority:  normal                   |  Milestone:  undecided
    Component:  code-network             |    Version:  1.10.0
   Resolution:  somebody else's problem  |   Keywords:  firewall tests
Launchpad Bug:                           |  foolscap
-----------------------------------------+---------------------------------
Changes (by exarkun):

 * status:  assigned => closed
 * resolution:   => somebody else's problem


Comment:

 I don't think that Unix domain sockets instead of TCP is a legitimate
 solution here.  Unix domain sockets are not TCP sockets.  They do not
 behave identically.  To the extent that either a Unix domain socket or a
 TCP socket can be used in the test suite, it *needs* to be a TCP socket.
 For tests the purpose of which is *not* to integration-test against the OS
 network stack, neither Unix domain sockets nor TCP sockets should be used.
 In-memory test doubles can be used instead.

 All that said, I don't understand what the ticket summary or description
 is suggesting or implying.  The test suite doesn't control what TCP ports
 on localhost will be connectable.  The environment of the test runner
 controls that.  If someone wants to run the test suite, they need a
 suitable environment.  Right now that environment is "ability to listen on
 unprivileged TCP ports on localhost and then connect to them".  If Tails
 disallows this, Tahoe-LAFS itself can't do anything about that.  The Tails
 operator must do something.

 My best guess at the suggestion in the ticket summary is that it should be
 possible to configure the test suite to only listen on certain TCP ports
 and then Tails can be configured to allow these to be listened on and
 connected to.  If that's the case, I'm not sure why Tails can't be
 configured to just allow the full ephemeral range.

 Please feel free to re-open with a clarification on that point, if one
 seems warranted.

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