News for hackers. Stuff that matters.
Re:What The Rails Security Issue Means For Your Startup by tomjen3 on Thursday January 31, 2013 @11:57AM (#5145885)
Actually it is the same issue as basically all other security issues in web programming (attack on crypto aside):

Failure to blacklist non-conforming input.

Really, it is that simple and that complicated.

Re:What The Rails Security Issue Means For Your Startup by dos1 on Thursday January 31, 2013 @12:15PM (#5145989)
Wouldn't whitelisting conforming input be a better approach? I realize it may be more difficult, but wouldn't that be more secure?

Edit: I'm genuinely interested - I always try and whitelist things when I'm building software. Although I have next to no background when it comes to security in particular.

Re:What The Rails Security Issue Means For Your Startup by purephase on Thursday January 31, 2013 @12:25PM (#5146046)
Whitelisting is what Rails did to get around the mass assignment issue. It was solved for awhile, it just was not the default configuration setting.

Whitelisting is what the rubygems folks are doing to work around this problem until a better implementation is put in-place in the YAML parser.

Generally, it is a better solution but it is more difficult and can break a lot of dependencies if not implemented correctly.

Re:What The Rails Security Issue Means For Your Startup by tomjen3 on Friday February 01, 2013 @06:49PM (#5154324)
Stupid me. I meant to write whitelisting.

Yes, you are absolutely right.