by CoachRufus87 on 12/21/16, 5:00 AM with 55 comments
by tinco on 12/21/16, 10:30 AM
We contacted the Rails team early on about this issue and worked closely with them to have this issue solved. Now that 5.0.1 is released we are at liberty to disclose details about this security issue.
I've written a blog post[2] on the problem, using OS X network shaping tools and a simple app to demonstrate it. Rails apps running on Passenger were never affected as Passenger implements response buffering for regular requests as well as websockets connections. Note that even popular reverse proxies like Nginx don't perform response buffering for websockets as far as I know, so this is something to be aware of if you're running on other frameworks than Rails as well.
[0] GH merge of patch: https://github.com/rails/rails/pull/26646
[1] GH related issue: https://github.com/rails/rails/issues/26409
[2] Blog post: https://blog.phusion.nl/2016/12/21/actioncable-under-stress-...
by jph on 12/21/16, 5:35 AM
Approximately hundreds of small bug fixes, across much of Rails. The fixes include some important ones for database types, time comparisons, thread issues, record reloading, etc.
IMHO these fixes address dozens of bugs that could cause major puzzlement for a typical Rails developer.
Thanks to all the contributors for excellent work on this release.
by Sivart13 on 12/21/16, 6:24 AM
by martijn_himself on 12/21/16, 11:52 AM
by JelteF on 12/21/16, 8:15 AM
by nickjj on 12/21/16, 12:52 PM
by pandafoo on 12/21/16, 9:33 AM
by wjossey on 12/21/16, 5:20 AM
by sergioocon on 12/21/16, 7:50 AM
Thanks!
by sergioocon on 12/21/16, 7:50 AM
Thanks!