News for hackers. Stuff that matters.
Re:Rails Commit: Whitelist all attribute assignment by default by Peaker on Monday March 05, 2012 @02:01AM (#3665725)
In other words:

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.

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.

Re:Rails Commit: Whitelist all attribute assignment by default by teyc on Monday March 05, 2012 @04:32PM (#3668441)
It is 2012, we should no longer have to debate about the acceptability of unvalidated inputs in a web application. Even PHP ditched register globals long ago.