Rails 1.1.5 is still broken, here's a workaround
Posted by Scott Laird Thu, 10 Aug 2006 16:28:07 GMT
Apparently Rails 1.1.5 is still broken. It fixed one attack but left a couple other holes open. Piers has a workaround that should work for any Rails app.
Now would be a great time to fix this, because the exploit is fairly obvious right now.

Should I take it as a bad sign that Piers’ site is throwing up 500 “Application error (Rails)” messages? :-)
Sigh. Bad timing–he just started an update and found a bug in some semi-unrelated work.
I got Rails 1.1.6 installed. What’s the cleanest way to force Typo to use it (instead of 1.1.5) ?
rake rails:freeze:gemsshould do it.