anchor.diff:  
   
   
  -That is one way to say it.  Of course, they could have easily just provided a Neo4j Enterprise binary without the intra cluster encryption turned off under it’s AGPLv3 license.
  +That is one way to say it.  Of course, they could have easily just provided a Neo4j Enterprise binary without 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.
    
  
positive.code: 
  Neo4j Enterprise is still free under its open source https://www.gnu.org/licenses/agpl-3.0.en.html[AGPLv3 license, window="_blank"]. However you may have noticed that you can no longer build the enterprise package binaries from the source code or download enterprise package binary with it's free https://www.gnu.org/licenses/agpl-3.0.en.html[AGPLv3 license, window="_blank"] from dist.neo4j.org.  Furthermore, if you use docker, https://github.com/neo4j/docker-neo4j-publish/commit/aa31654ee8544cd544b369d2646cf372086f7b70[you must now accept a 'commercial agreement’ before proceeding, window="_blank"].  In other words, official Neo4j docker images are no longer packaged with the free https://www.gnu.org/licenses/agpl-3.0.en.html[AGPLv3, window="_blank"] licensed binaries.  
  
  Neo4j Enterprise 'binaries’ are simply the packaged Neo4j distributions you download and run on your computer, server, container, etc.   For the 3.3.0 release the binary package file names would be https://dist.igovsol.com/neo4j-enterprise-3.3.0-unix.tar.gz[neo4j-enterprise-3.3.0-unix.tar.gz , window="_blank"] for the Linux package and https://dist.igovsol.com/neo4j-enterprise-3.3.0-windows.zip[neo4j-enterprise-3.3.0-windows.zip , window="_blank"] for the windows package. (The links above point to the binaries we packaged with the AGPLv3 license.)
  
  Why has Neo4j made it harder to access the open source enterprise binaries? 
  
  