I’ve been looking through the code you have in your packages, and I see that most of what you have for authc/authz is based on Searchguard, however there’s no attribution to Searchguard. This is in contrast to what you have done here: GitHub - opendistro-for-elasticsearch/sql: 🔍 Open Distro SQL Plug…

Hi Mikael. The security features include contributions by floragunn (the makers of Search Guard) and you will see their copyrights on the source files. We have collaborated with them on bringing security features to Open Distro.

I saw taht you are using Search Guard Enterprise modules code without attribution in your security-advanced-modules repo. Does this means that this code is now AWS code and under Apache licence or I still have to buy licence from floragunn?

Hi @potrosni , all of the plugins included in Open Distro for Elasticsearch are licensed under the Apache License, Version 2.0.

I noticed that there is Lawsuits against Floragunn by Elasticsearch. [image] Dear Search Guard Users What is the impact on Opendistro security plugin also developed by Floragunn?

I am also curious if there are any ramifications

Why no attribution to Searchguard?

General Feedback

ckressin March 21, 2019, 7:12pm 5

We have helped AWS to bring security features to Open Distro for Elasticsearch. From our perspective Open Distro for Elasticsearch is a legitimate product.

Claudia Kressin
CEO, floragunn GmbH

Topic		Replies	Views
Elastic suing SearchGuard General Feedback	4	4755	September 18, 2019
Need a license for "enterprise modules"? General Feedback	7	1874	March 14, 2019
OpenDistro-- Are Plugin Features open source? Open Source Elasticsearch and Kibana	4	513	February 22, 2021
Functionalities & Licences & Pricing Open Source Elasticsearch and Kibana	3	2262	March 13, 2019
Use only the security features as a module/plugin for an existing ELK stack setup? Security	2	903	February 24, 2021

Why no attribution to Searchguard?

Related topics