Re:Ruby on Rails vulnerable to mass assignment and SQL injec...
by obstacle1 on Monday February 11, 2013 @07:32PM
(#5204409)
I'm not parent, but the claim wasn't that popular implies vulnerable. Just that some projects ignore security while the stakes are low, which comes back to bite them in the backside once adopters pick up (e.g. what we're witnessing with Rails now).
Re:Ruby on Rails vulnerable to mass assignment and SQL injec...
by nostrademons on Tuesday February 12, 2013 @02:57AM
(#5205727)
...which is often the right choice, because projects that pay attention to security from the get-go often lose out in the marketplace to ones who pay attention to other, more important factors. There's an opportunity cost to everything, and for many apps, security is not as important as convenience, ease-of-use, performance, or features.
Witness Dropbox vs. TarSnap. Dropbox has had multiple serious security vulnerabilities published. TarSnap is by the FreeBSD security officer. Yet Dropbox is the one with the million+ users and $B+ market cap, because grandma cares a lot more about being able to figure out how to use the product than about what happens when the product gets hacked.
Re:Ruby on Rails vulnerable to mass assignment and SQL injec...
by cookiecaper on Tuesday February 12, 2013 @07:26AM
(#5206338)
There's a lot more to DB v. TS than "Dropbox focused less on security". They're different programs for different audiences. While in some cases they may have market overlap, TS definitely has a niche that would never even consider DB as a possibility. TS's major competitor is custom solutions like rsync.net + duplicity.
Just because a platform is small doesn't mean somebody isn't going to try and bust it and when they do the small project may not have the resources to push out a robust fix quickly.