[nanomsg] Re: Port sharing, tcpmux, web-related roadmap et c.

  • From: Martin Sustrik <sustrik@xxxxxxxxxx>
  • To: nanomsg@xxxxxxxxxxxxx
  • Date: Fri, 21 Nov 2014 11:33:42 +0100

On 2014-11-20 22:57, Matthew Hall wrote:
Could we use Coverity Scan: https://scan.coverity.com/ to check the daemon for 
any security problems, etc.?
Yes, we can, but the implementation is 2 days old so you can spot problems even by looking at the code.
In general a port-mapping daemon is helpful to making dependable distributed applications... Java uses JNDI for this among other mechanisms. There are various Amazon S3 based mechanisms for doing service location in the cloud, 
there is SLP, etc. etc.
Keep in mind that tcpmux is only a local service that maps service name to a process that provides the service. It's pretty much the same thing that TCP implementation does, mapping src/dst port pairs to individual TCP sockets. 

Distributed service location services are much more complex stuff.
Are there ways to get the daemon to open ephemeral / proxied sockets (not sure what the proper word is), from a known-good range where FW ACL's are open? Can you get it to cycle through the predictable pool, and what happens when it 
empties the valid-socket pool?
Not sure what you mean. Keep in mind that tcpmux is just plain old TCP, except that connection establishment mechanism is slightly extended to use port+service instead of port alone. 

Martin

Other related posts:

  1. Home
  2. nanomsg
  3. Archive
  4. 11-2014