6 ms·
You expected a database sitting on the public internet to be secure? A very young one, no less? Who is downvoting this? People who hate common sense?
by peterwwillis 10y ago
You expected a database sitting on the public internet to be secure? A very young one, no less?
Who is downvoting this? People who hate common sense?
- abiox 10y agoi can't downvote, but your question seemed like a nonsequitur.
- jasondc 10y ago+1 Ideally, databases should never have internet access
- monksy 10y agoTell that to frontend javascript devs who think they don't need a back end system. Without a public facing DB they're pretty much dead in the water.
- bartread 10y agoThe more things change, the more they stay the same. I'm thinking of people who back in the 90s/early noughties didn't want to bother with a middle tier application, and instead talk directly to the database from their fat clients(1) because it was easier. (1) This, btw, is what many SPA are: fat client apps running within a browser. When I came back to web development four years ago one of the biggest surprises was how much like desktop development it had become in many ways.
- cm2187 10y agoIf you are using one of the main cloud provider, the database they provide will almost always do. For azure at least, they protect it with a firewall that block all IPs by default. But a database with no internet access is unrealistic.
- ivanhoe 10y agoHow about expecting that DB doesn't bind to 0.0.0.0 by default and to force passwords to be set during the installation? Is that such an unreasonable thing to expect?
- peterwwillis 10y agoYes. Expecting anything to be secure by default is unreasonable. It would be nice, but I would not just expect it, I would confirm it. Expecting it to be secure on the internet is even less reasonable.
- ivanhoe 10y agoI'm not talking about it being "secure by default". Just not being obviously insecure by default is more than enough...