Rails 1.1.5 has been released today, but there are no new features. It's important, however, as it contains a number of bug fixes and a 'mandatory security patch' which David Heinemeier Hansson, creator of Rails, claims is significant:
This is a MANDATORY upgrade for anyone not running on a very recent edge (which isn’t affected by this). If you have a public Rails site, you MUST upgrade to Rails 1.1.5. The security issue is severe and you do not want to be caught unpatched.
Even though details of the security flaws are not officially being given, it wouldn't take a would-be hacker long to run a diff between 1.1.4 and 1.1.5, so if you're running Rails 0.13 through 1.1.4, upgrade as soon as possible. For more information see David's post at the official Rails blog.
/filters:no_upscale()/sponsorship/topic/25afca57-6bcb-4c42-9a70-fbea10ce4fc7/MicrosoftLogoRSB-1678874949003.png)
/articles/visual-thinking/en/smallimage/LOGO-1679339789328.jpg){kind=logo}
/articles/framework-architectural-decisions/en/smallimage/logo-1679060242842.jpg){kind=logo}
/articles/asp-dotnet-minimal-apis/en/smallimage/logo-1678972581766.jpg){kind=logo}
/presentations/staff-plus-open-source/en/smallimage/alex-porcelli-s-1679038616213.jpg)
/presentations/java-compiler-intermediate-representation/en/smallimage/chris_seaton-s-1679038354209.jpg)
/articles/technology-carbon-impact/en/smallimage/logo-1678865261490.jpg){kind=logo}
/articles/lambda-migration-k8s-jobs/en/smallimage/logo-1678732894614.jpg){kind=logo}
/articles/istio-ambient-mesh/en/smallimage/logo-1678364642232.jpg){kind=logo}
/articles/contract-driven-adoption/en/smallimage/logo-1678427061074.jpg){kind=logo}
Community comments
Don't forget to change your config/environment.rb...
by Tom Copeland,
What does it take for a cracker to find the critical change ?
by anjan bacchu,
Re: What does it take for a cracker to find the critical change ?
by Peter Cooper,
It appears the way the notice was handled left something to be desired
by Obie Fernandez,
A fairly comprehensive explanation
by Obie Fernandez,
Don't forget to change your config/environment.rb...
by Tom Copeland,
Your message is awaiting moderation. Thank you for participating in the discussion.
...if you've set a RAILS_GEM_VERSION version there, that is. And doing a "gem cleanup" will keep things tidy too.
What does it take for a cracker to find the critical change ?
by anjan bacchu,
Your message is awaiting moderation. Thank you for participating in the discussion.
hi there,
"Even though details of the security flaws are not officially being given, it wouldn't take a would-be hacker long to run a diff between 1.1.4 and 1.1.5, so if you're running Rails 0.13 through 1.1.4, upgrade as soon as possible."
you mean, cracker, don't you ?
BR,
~A
Re: What does it take for a cracker to find the critical change ?
by Peter Cooper,
Your message is awaiting moderation. Thank you for participating in the discussion.
If I were talking as a geek to geeks, yes. As a writer who tends to stick to the standard vernacular and whose audience contains many non-geek types, no, sadly. :)
It appears the way the notice was handled left something to be desired
by Obie Fernandez,
Your message is awaiting moderation. Thank you for participating in the discussion.
Ben Griffiths does a good job of deconstructing the official reaction.
A fairly comprehensive explanation
by Obie Fernandez,
Your message is awaiting moderation. Thank you for participating in the discussion.
Explanation of the security hole.
It's worth noting that a properly secured and configured server should not be affected by this problem. Neither are the hundreds, if not thousands, of "enterprisey" IT apps that live behind a corporate firewall.
Notwithstanding, this is a major news event and I am trying to compile a list of comments from people running major Rails deployments to see how they were affected, if at all.