title: Node.js TLS connections without hostname verification
body: <p>I'm playing with a swarm of "nodes" connecting to each other, and all I really care for is that they are connected securely to each other and are all authenticated.</p>
  
  <p>For this I figured the TLS module would be a good fit. I created a CA and signed a bunch of certificates, one for each node. I then hit the issue that certificates are now validated against the host from which the node connects.</p>
  
  <p>Is it possible somehow to disable or work around the Common Name validation?</p>
  
  <p>Is there something fundamentally flawed about this setup?</p>
  
  <p>Am I correct that, as long as these certificates are signed by my CA, the connection should be secure and I am certain only my nodes can connect?</p>
  
  <p>It seems like just an annoyance having to sign certificates locked to a hostname or IP (or several in case of multiple interfaces). I've learned that the requirement to validate the host is actually not a part of TLS but HTTPS - in that light, it might be a Node.js bug to do so by default?</p>