News for hackers. Stuff that matters.
Re:Amazon: Not OK – Why we had to change Elastic licensing by joshuaissac on Tuesday January 19, 2021 @04:19PM (#25839012)
> I read that article [...] If they had actual proof, they would take legal action against the author of that plugin.

The first sentence of that article:

> Back on September 4th, we filed a lawsuit against floragunn GmbH, the makers of Search Guard, a security plugin for Elasticsearch

Re:Amazon: Not OK – Why we had to change Elastic licensing by nenolod on Tuesday January 19, 2021 @05:27PM (#25839774)
Yeah? SCO sued a bunch of people too. They haven't won, though.
Re:Amazon: Not OK – Why we had to change Elastic licensing by joshuaissac on Tuesday January 19, 2021 @06:25PM (#25840377)
Elastic and Floragunn are unrelated to SCO.
Re:Amazon: Not OK – Why we had to change Elastic licensing by nenolod on Tuesday January 19, 2021 @07:15PM (#25840873)
They share a similarity: the Floragunn litigation is unresolved (and clearly Floragunn continues to distribute their plugin). SCO, too, failed to resolve their litigation favorably to SCO.
Re:Amazon: Not OK – Why we had to change Elastic licensing by joshuaissac on Tuesday January 19, 2021 @07:55PM (#25841205)
That is a very tenuous connection. Floragunn has not resolved the litigation in their favour, either.

If we are going off similarities, Napster also continued to distribute their software while their lawsuit involving the RIAA was unresolved. The court still ruled against them eventually.