News for hackers. Stuff that matters.
Re:Open Distro for Elasticsearch by ssgao on Monday March 11, 2019 @02:11PM (#19361267)
For SearchGuard, only the basic auth is Apache 2.0. Anything practical you need to pay to use it.
Re:Open Distro for Elasticsearch by termez442 on Tuesday March 12, 2019 @04:54AM (#19366387)
From a look at the source code, Amazon has Apached 2.0 the entire Floragunn Searchguard codebase (including the commercial part)
Re:Open Distro for Elasticsearch by sagichmal on Monday March 11, 2019 @02:17PM (#19361327)
Why isn't AWS paying to use it, then? It's not like they don't have the money?
Re:Open Distro for Elasticsearch by tragicpapercut on Monday March 11, 2019 @02:38PM (#19361553)
It's not just about AWS, other people need to use this as well. Why are security features a paid for addition? Why not make core features a paid for addition instead? I've always hated Elastic (the company) for this decision, please stop trying to give away free things that are not secure, and then charge for security.
Re:Open Distro for Elasticsearch by _msw_ on Monday March 11, 2019 @02:40PM (#19361581)
I'd recommend browsing the code to find out more about the security module:

https://github.com/opendistro-for-elasticsearch/security/blo...

Re:Open Distro for Elasticsearch by ssgao on Monday March 11, 2019 @02:36PM (#19361526)
there's no "they", there's only us. AWS paying to use it means we are paying to use it. Between that and a truly Apache 2.0 project, I think it's a no-brainer for everyone.
Re:Open Distro for Elasticsearch by sagichmal on Monday March 11, 2019 @02:43PM (#19361614)
Why shouldn't you pay to use it, then?

More generally: why should AWS get to leverage its near-monopolistic position in the SaaS market to perform essentially hostile takeovers of the software projects it packages and runs? Simply because they have the resources to do it?

Re:Open Distro for Elasticsearch by e1ven on Monday March 11, 2019 @04:57PM (#19362753)
I'm very glad that they've done this.

The code was open, and the company decided to close it for the new versions, so it forks. Forks are common when people don't like the corporate direction of an OSS project - It's a strength, not a weakness. Openoffice/Libreoffice, Hudson/Jenkins etc.

Imagine if Linus said that the next version of Linux would be paid-only.

Within 15 minutes there'd be a new librelinux repo that people could contribute to instead.

Someone was going to make a new fork anyway - This is Amazon putting their money where their mouth is to fund and support that new fork.

Re:Open Distro for Elasticsearch by dhd415 on Monday March 11, 2019 @05:27PM (#19362998)
To be clear, no Elasticsearch code or features that were OSS were closed. As new Elasticsearch features are developed, some of them are now released as OSS and others are released with a commercial license.
Re:Open Distro for Elasticsearch by anth_anm on Monday March 11, 2019 @11:13PM (#19365067)
Okay, are you glad that Amazon now owns Elasticsearch?
Re:Open Distro for Elasticsearch by therealx on Monday March 11, 2019 @08:16PM (#19364197)
If ES didn't do the weird license change thing, we wouldn't be here. Either Amazon wouldn't have used it, or they'd be paying. Including non-com features in the default install was not a good way to play things.

Would you feel the same if AWS built a drop in/api compatible system from scratch?