News for hackers. Stuff that matters.
Re:The MongoDB hack and the importance of secure defaults by nailer on Wednesday January 11, 2017 @12:32PM (#13375667)
By this standard, every programmer who puts an app into production without understanding assembly is not technically sophisticated.

We could expect every programmer to have domain knowledge of databases, even when it's not normally needed to operate one.

Or we could just make databases not acknowledge writes that haven't happened, not listen on all ports, not hide information about data loss in non-clustered setups deep inside the documentation.

Counterargument: many people who are good at a particular topic enjoy feeling superior to people who don't have their knowledge.

Re:The MongoDB hack and the importance of secure defaults by hitgeek on Wednesday January 11, 2017 @01:03PM (#13375948)
at the time these versions of mongodb were released, it was only a few years old, and DID require considerable domain knowledge to run in production. This does not seem unreasonable for new immature technologies.

unfortunately, I don't think this was always communicated effectively by the explosion of mongodb marketing and hype.

Re:The MongoDB hack and the importance of secure defaults by nailer on Thursday January 12, 2017 @11:11AM (#13383354)
> DID require considerable domain knowledge to run in production.

What do you mean? If you you mean it took knowledge to run per se: it didn't: unzip and run the service, it's up. It wasn't any more complex than any other piece of software.

Or do you mean it did require considerable knowledge to avoid data loss on software marked as 'stable'? Yes, that's the problem, and yes, that's unreasonable.