Re:Rails Commit: Whitelist all attribute assignment by default
by teyc on Sunday March 04, 2012 @07:38PM
(#3664778)
Lack of humility.
[ Parent
| on HN ]
Re:Rails Commit: Whitelist all attribute assignment by default
by Volpe on Sunday March 04, 2012 @09:29PM
(#3665133)
That's a bit harsh, it is at least a grey area.
Mass-assignment by-default, with disabling fields you want to protect
vs
Mass-assignment off by default, with enabling fields you want to mass-assign.
It's hardly just outright arrogance.
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.