http://www.engineyard.com/blog/2009/bigdecimal-vulnerability-in-ruby-186-and-187/ Wed, 08 Feb 2012 12:12:12 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://www.engineyard.com/blog/2009/bigdecimal-vulnerability-in-ruby-186-and-187/comment-page-1/#comment-3100 Michael Mullany Thu, 11 Jun 2009 16:40:05 +0000 http://www.engineyard.com/blog/?p=1267#comment-3100 Alex, if you are a slice/cluster customer, please open a ticket with support to arrange a maintenance window to be upgraded. We do not patch customer environments without consent.. Alex, if you are a slice/cluster customer, please open a ticket with support to arrange a maintenance window to be upgraded. We do not patch customer environments without consent..

]]> http://www.engineyard.com/blog/2009/bigdecimal-vulnerability-in-ruby-186-and-187/comment-page-1/#comment-3033 Alex Le Thu, 11 Jun 2009 15:21:35 +0000 http://www.engineyard.com/blog/?p=1267#comment-3033 For existing customers with live production application, do you have an ETA to apply the fix? And how long the application would be taken down while the fix is applied? For existing customers with live production application, do you have an ETA to apply the fix? And how long the application would be taken down while the fix is applied?

]]> http://www.engineyard.com/blog/2009/bigdecimal-vulnerability-in-ruby-186-and-187/comment-page-1/#comment-2175 BigDecimal Vulnerability in Ruby 1.8.6 and 1.8.7 « Engine Yard Status Wed, 10 Jun 2009 16:49:49 +0000 http://www.engineyard.com/blog/?p=1267#comment-2175 [...] upgrading your slices to a patched version as soon as possible. For more information please see http://www.engineyard.com/blog/2009/bigdecimal-vulnerability-in-ruby-186-and-187/. « [...] [...] upgrading your slices to a patched version as soon as possible. For more information please see http://www.engineyard.com/blog/2009/bigdecimal-vulnerability-in-ruby-186-and-187/. « [...]

]]>