http://www.matasano.com/log/1079/rubys-vulnerability-handling-debacle/
Ezra: none of the official releases are non segfaulting, we're running p114 with backported sec patches -Matt On Tue, Jul 1, 2008 at 9:01 PM, Matt Aimonetti <[EMAIL PROTECTED]> wrote: > I heard a lot of people not recommending to switch to 1.8.7 since it > backported some stuff from 1.9 and broke some 1.8.x stuff > I believe the segfault you are referring to were noticed by a lot of > people, Engine Yard had a patch but I don't know if it got merged in. > > -Matt > > > On Tue, Jul 1, 2008 at 8:25 PM, Rob Kaufman <[EMAIL PROTECTED]> wrote: > >> >> Hi Cheri, >> Looks like current 'Stable' Ruby is Ruby 1.8.7-p22... are you sure >> the issue wasn't already fixed? Also how confidant are you that >> you're dealing with a Ruby bug and not a packaging bug. Often when >> something is seen by just a few linux users, it is in the (Debian, >> Ubuntu, Fedora, Gentoo, etc) package and performance patches and not >> in the Ruby code itself. If it were me, I would download the latest >> stable, complile it, and then try starting script/server with that >> Ruby version. If that works, then install that version and off you go >> =-) >> >> Rob >> >> On Tue, Jul 1, 2008 at 11:08 AM, liquid_rails <[EMAIL PROTECTED]> >> wrote: >> > >> > Does anybody know how long it generally takes the Ruby Core Team to >> > come up with a fix for bugs like this, or if they're even working on >> > it? >> > >> > >> http://rails.lighthouseapp.com/projects/8994/tickets/513-segmentation-fault-ruby-1-8-6-i686-linux-patchlevel-230#ticket- >> > >> > Thanks, >> > >> > Cheri >> > > >> > >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby -~----------~----~----~----~------~----~------~--~---
