3 ms·
The underlying issue here is that Firebase was sold as the answer to the not-so-techy people that wanted to create apps but couldn't necessarily handle the back
by yohann305 8y ago
The underlying issue here is that Firebase was sold as the answer to the not-so-techy people that wanted to create apps but couldn't necessarily handle the backend and here the issue is that Firebase should have thought that the majority of the audience thought Firebase would handle backend security for them as well.
Yes, Firebase team messed up here, but technically speaking it's not too late to fix if done right now. I noticed Firebase already added big banners in Firebase dashboard to make people aware of this issue, or maybe it's a way for Firebase team to cover their asses by saying we told you so!!
It's a good step towards fixing this issue but it's still not enough.
- sdhgaiojfsa 8y agoThat is not a very good take. There have been dozens if not hundreds of similar leaks from people who thought they could handle the backend and used more traditional technologies. There's precious little evidence that I'm aware of that these apps are systemically less secure than apps that use bespoke backends.
- baybal2 8y ago>The underlying issue here is that Firebase was sold as the answer to the not-so-techy people Very explanatory
- filleduchaos 8y agoWhat on earth? Firebase has had the notice that your database is open to public access (if set that way) for ages. They've had IAM rules for years.