Was there any special about the 1.8.7 that was shipped with 8.10? One of
our users is hitting this error, but our test case to detect the buggy
version is not firing, even though it works fine for the 1.8.7 release
from the ruby web site:
#
# Check for the ugly 1.8.7 short-named constants bug
#
c
>From the looks of it, even though the behavior is different between
1.8.6 and 1.8.7-patched, it was addressing an ambiguity in the first
place and the 1.8.7-patched behavior should be considered correct. The
8.10 release has shipped with the broken 1.8.7 interpreter and no way
for users to downgra
Patch: http://svn.ruby-lang.org/cgi-
bin/viewvc.cgi?view=rev&revision=18485
Test Case: http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-
dev/35116
(thanks Antoine!)
--
Ruby 1.8 package breaks the Metasploit Framework (short-named constants)
https://bugs.launchpad.net/bugs/282302
You recei
I was not able to trigger this with a standalone test case, but it is
easy to reproduce using the svn version of the Metasploit Framework. The
example below assumes you have a Windows server somewhere with port 135
open:
$ svn co http://metasploit.com/svn/framework3/trunk/ msf3
$ ruby msf3/msfcli
Sure, let me write a script that demonstrates the bug, its a little
tricky because it only occurs in some convoluted Ruby objects (classes
which inherit from mixins which define short-name constants, with a
different base class than the class which includes them). I had a link
to the Ruby patch whi
Public bug reported:
Binary package hint: ruby1.8
The current stable release of the Ruby interpreter (1.8.7 in Ibix)
breaks any software using short-named constants. The latest stable
version from ruby-lang.org has this issue as well, but it has been fixed
in the latest stable snapshot.
To summa
