anchor.diff:  ----
   
       
  -https://github.com/neo4j/neo4j/blob/3.3/enterprise/causal-clustering/src/main/java/org/neo4j/causalclustering/discovery/HazelcastClientConnector.java[3.3 release code , window="_blank"]  :  The sslPolicy initialization has disapeared .
  +https://github.com/neo4j/neo4j/blob/3.3/enterprise/causal-clustering/src/main/java/org/neo4j/causalclustering/discovery/HazelcastClientConnector.java[3.3 release code , window="_blank"]  :  The sslPolicy initialization has disappeared.
       
   [source,java]
   ----
  +
       HazelcastClientConnector( Config config, LogProvider logProvider, HostnameResolver hostnameResolver )
           {
               this.config = config;
  
positive.code: 
  
  
  That is one way to say it.  Of course, they could have easily just provided a Neo4j Enterprise binary with the intra cluster encryption turned off under it’s https://www.gnu.org/licenses/agpl-3.0.en.html[AGPLv3 license, window="_blank"].  
  
  Security critical components should be open source, security by obscurity has proven not to be a good strategy in the past.
   
  Right now the only difference between the paid Neo4j Enterprise (commercial) binary and Neo4j Enterprise (open source) binary is that intra cluster encryption is turned on in the commercial version and is turned off in the open source binary.  
  How many of you are actually using causal clustering in production?  Well - if you upgrade to 3.3.0 and don't turn it back on yourself , you may be a little less secure assuming you aren't using encrypted tunnels / vpn, etc between your cluster nodes.
  
  
  
  
negative.code: 
  Back to the core of this post.   So what has Neo4j Inc done to limit your access to Neo4j Enterprise binaries packaged with the free open source https://www.gnu.org/licenses/agpl-3.0.en.html[AGPLv3 license, window="_blank"]?
  
  *Action 1*:  The enterprise packaging build instructions https://github.com/neo4j/neo4j/commit/affe1a0b4ab47c9d4673bfa507868ccd03c48ddd[were removed from the code base , window="_blank"].   Until the 3.3.0 release,  anyone could have checked out the https://github.com/neo4j/neo4j[Neo4j source code from github , window="_blank"], and run a few simple commands to build the Neo4j Enterprise binaries complete with the https://www.gnu.org/licenses/agpl-3.0.en.html[AGPLv3 license, window="_blank"].   That’s not the case anymore.  If you run the build commands on the 3.3.0 branch you will notice that only the Neo4j Community Edition binary is present after the build process completes.  Who really uses Neo4j Community Edition once they realized Neo4j Enterprise edition is also free?  
  
  The packaging system simply provides the instructions on how to ‘build’ the Neo4j Enterprise distribution binary, much like the instructions you get with furniture purchased at IKEA.    All the artifacts that are used to build the Neo4j Enterprise binary are all open source, but the instructions explaining how to put together these artifacts have disappeared.   
  
  *Action 2*:  Neo4j Inc slipped a commercial license into the binaries found on their distribution site that is used for docker images.  Until now, if you wanted to download the Neo4j Enterprise binary from Neo4j Inc directly, you could have done so using the distribution site which is publically available. It just isn't advertised for obvious reasons.     
  
  Those who were using the official docker images or downloading the enterprise binary directly from dist.neo4j.org were in for a surprise when they were forced to accept commercial terms in order to access the distributions.  
  
  Want to see for yourself - download the http://dist.neo4j.org/neo4j-enterprise-3.3.0-unix.tar.gz[Neo4j Enterprise binary, window="_blank"] which Neo4j Inc packages and take a look at the LICENSE.txt file.
  
  Instead of the standard https://www.gnu.org/licenses/agpl-3.0.en.html[AGPLv3 license, window="_blank"] which used to be there, the LICENSE.txt file now says:
  
  