News for hackers. Stuff that matters.
Re:The MongoDB hack and the importance of secure defaults by bqe on Wednesday January 11, 2017 @12:07PM (#13375449)
This is also the case for Elasticsearch. In fact, to get a proper username/password/ACL setup, you need to pay for professional support.
Re:The MongoDB hack and the importance of secure defaults by reqres on Wednesday January 11, 2017 @12:20PM (#13375556)
IIRC, there was also a time when Elasticsearch used multicast by default to detect other ES nodes on the network and to add them to the cluster automatically. So any node joining the same network will join a cluster and have shards allocated to it
Re:The MongoDB hack and the importance of secure defaults by hinkley on Wednesday January 11, 2017 @01:04PM (#13375953)
Early J2EE frameworks did that too. Super fun when your dev box clusters with a coworker and undoes your regression testing because half of the tests run on an older version of the code!
Re:The MongoDB hack and the importance of secure defaults by sneakymichael on Wednesday January 11, 2017 @02:17PM (#13376647)
It seemingly still does; I'm just getting started with Elasticsearch & your description aligns with what I've read in the introduction guide
Re:The MongoDB hack and the importance of secure defaults by polyfractal on Wednesday January 11, 2017 @03:08PM (#13377080)
Just FYI, multicast discovery was moved to a plugin in v2.0 [1], deprecated in v2.2 [2] and removed entirely in v5.0 [3]

- [1] https://www.elastic.co/guide/en/elasticsearch/reference/2.0/...

- [2] https://www.elastic.co/guide/en/elasticsearch/plugins/2.2/di...

- [3] https://www.elastic.co/guide/en/elasticsearch/plugins/5.1/di...