News for hackers. Stuff that matters.
Re:Multiple vulnerabilities in parameter parsing in Action Pack by mikeycgto on Tuesday January 08, 2013 @03:55PM (#5028460)
If you've recently started a new Rails project (or are thinking about it), you should use strong_parameters right off the bat!
Re:Multiple vulnerabilities in parameter parsing in Action Pack by joevandyk on Tuesday January 08, 2013 @06:19PM (#5029135)
I'm not 100% positive, but I don't think strong_parameters would do anything to protect you here.
Re:Multiple vulnerabilities in parameter parsing in Action Pack by steveklabnik on Tuesday January 08, 2013 @06:27PM (#5029175)
It would not have helped with this vulnerability, no. But it is a better way of handling filtering appropriate parameters.
Re:Multiple vulnerabilities in parameter parsing in Action Pack by pekk on Tuesday January 08, 2013 @04:18PM (#5028580)
Why is strong_parameters not the only way? Rails is pretty opinionated in many other respects...
Re:Multiple vulnerabilities in parameter parsing in Action Pack by bratsche on Tuesday January 08, 2013 @04:29PM (#5028630)
It was opinionated to use attr_accessible until a better approach came along. Beginning in 4.0 it will be opinionated to use strong_parameters, but they can't just take attr_accessible away because a lot of people are upgrading apps.
Re:Multiple vulnerabilities in parameter parsing in Action Pack by jenius on Tuesday January 08, 2013 @04:28PM (#5028623)
It will be the default in rails 4... so soon : )
Re:Multiple vulnerabilities in parameter parsing in Action Pack by steveklabnik on Tuesday January 08, 2013 @04:46PM (#5028708)
The downside of 'don't break APIs for minor version changes' means that you can't break APIs until the major version changes. ;)
Re:Multiple vulnerabilities in parameter parsing in Action Pack by steveklabnik on Tuesday January 08, 2013 @04:02PM (#5028496)
Agreed! That is what I teach when I do training.