search-guard-enterprise-modules

This is the commit containing the code that Elastic says was copied by Search Guard: https://github.com/floragunncom/search-guard-enterprise-modu... In particular, the change to getLiveDocs(): https://github.com/floragunncom/search-guard-enterprise-modu... and numDocs(): https://github.com/floragunncom/search-guard-enterprise-modu... EDIT: At least in the case of numDocs(), both Elastic and Search Guard's implementations seem to be based on this bit of Apache-licensed code from Lucene (or perhaps this is just a common pattern for counting live documents?): https://github.com/apache/lucene-solr/blob/branch_6_3/lucene...

Amazon has forked more than the community version of Search Guard, see by yourself: https://github.com/floragunncom/search-guard-enterprise-modu... https://github.com/opendistro-for-elasticsearch/security-adv... They just forked the full code base and tried to remove any reference of Search Guard. I am not sure what really happened here but this smells fishy.

If you look for real FOSS ES security i recommend Search Guard https://github.com/floragunncom/search-guard . This is a ASL2 licensed repo which provide all kinds of basic security for Elasticsearch including SSL/TLS. So the content in this repo are real fully "open source". Then there is a second non-FOSS repository https://github.com/floragunncom/search-guard-enterprise-modu... which contains all the enterprise/advanced stuff. The code is open but not "open source". So FOSS and and non-FOSS/proprietary are well separated. I don't understand why elastic mix and merge FOSS and non-FOSS code in the same repo with a weird mixed license applicable for special folders. This all makes no sense to me. And there are several other FOSS projects which provide x-pack like functionalities described here https://sematext.com/blog/x-pack-alternatives/