Re:Rails Commit: Whitelist all attribute assignment by default
by rapind on Monday March 05, 2012 @12:39PM
(#3667377)
This seems like an intentional oversimplification. Having mass-assignment on by default and therefore requiring the developer to create a whitelist of attributes for each of their models has a complexity cost associated with it. Failing to mention this at all shows a lack of objectivity.
I happen to believe it's worth it for the increased security, however I'm not going to pretend that there isn't an associated cost.
Security vulnerabilities by default, with the ability to patch the vulnerability on a project-by-project basis.
vs
Security by default, with the ability to allow potentially insecure assignment on fields you want to assign.