RoR遭遇嚴重的安全危機！

?SearchAppSecurity.com story?報道了RoR的一個嚴重的安全漏洞，致使開發者不得不迅速推出一個安全補丁的版本，而且該版本需要強制升級。

由于這個錯誤非常嚴重，以至開發者不得不隱藏這個漏洞的細節，所以升級過程中的人們無法知道如何預防該漏洞帶來的攻擊。

? 這樣的官方發布的安全問題，可謂是給RoR狂熱撲了一盆大冷水。RoR的開發者們甚至嚇得都不敢公開的這個錯誤。然而這個錯誤只是一個開始，還遠遠沒有結 束。從windows，j2ee，php任何開發都經歷過這個過程。而他們都趨于穩定，尤其是j2ee,php在unix下的安全架構更是非常可靠，我們 積累了大量這個領域進行防范的經驗。

原文地址：http://blog.csdn.net/danny_xcz/archive/2006/08/11/1049441.aspx

-----------------------------------------------------------------------------------------------------------------------

Ruby on Rails experiences serious security breach

A serious security vulnerability has forced the creators of Ruby on Rails to issue an immediate upgrade for the software. Version 1.1.5, which is being called a mandatory upgrade, is available now.

Rails 1.0 and prior, as well as 1.1.3, are not affected. The creators are still trying to determine how contaminated 1.1.0, 1.1.1, 1.1.2, and 1.1.4 are.

The vulnerability is so critical that the creators aren't disclosing any details so as to prevent attacks and protect people who are still in the process of upgrading.

From on the Riding Rails blog: "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."

Rails 1.1.5 is fully drop-in compatible with 1.1.4. It includes only a few bug fixes and no new features.

"As always, the trick is to do 'gem install rails' and then either changing config/environment.rb, if you're bound to gems, or do "rake rails:freeze:gems" if you're freezing gems in vendor," according to the advisory in the blog posting.

The creators are continuing their investigation into the breach and promise to issue a full report once it's complete and people have had enough time to upgrade.

附：Groovy輕松入門——Grails實戰之GORM篇