Re:New ‘Meow’ attack has deleted almost 4k unsecured databases
by dredmorbius on Sunday July 26, 2020 @11:07PM
(#23961909)
If your assumptions are repearedly demonstrated invalid they are wrong.
Change them.
Re:New ‘Meow’ attack has deleted almost 4k unsecured databases
by bigiain on Monday July 27, 2020 @02:35AM
(#23962699)
Personally, I reckon that applies at least as much (if not more) to the devs installing random software packages onto internet connected and un-firewalled servers - as it does to database developers who document clearly that their software is not intended and is actively unsafe to install on directly internet connected servers...
Cave ne recipiens donum...
Re:New ‘Meow’ attack has deleted almost 4k unsecured databases
by dredmorbius on Monday July 27, 2020 @04:10AM
(#23963121)
If a thing should not be run in a given configuration then it should not be runnable in that configuration.
The vendor / developer has both awareness and capability to ensure this.
I have a bunch of fairly important personal documents in a filing cabinet with no lock. And I'm perfectly fine with that. I wouldn't keep it in my front yard, because that's obviously stupid, but keeping it inside behind my locked door and upstairs in my office? A perfectly acceptable risk (for me and my files).
I do agree that ElasticSearch do a quite poor/irresponsible job of pointing out their cabinet has no lock. I think Redis do a better job, but are seriously let down by all the internet tutorials that just say "sudo yum install redis" as a minor intermediate step in getting example-todo-list-de-jour working - without even a footnote explaining that anybody who actually visited the redis site now has instructions on how to p0wn your box. ( http://antirez.com/news/96 ) I do think the "Securing Redis" section of this page - https://redis.io/topics/quickstart - deserves to be much closer to the top - I'd have put it before the how to download/install/start instructions myself (though I _think_ recent versions of redis only bind to localhost in the default config, maybe?)