CVE-2011-2705 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-2705): The SecureRandom.random_bytes function in lib/securerandom.rb in Ruby before 1.8.7-p352 and 1.9.x before 1.9.2-p290 relies on PID values for initialization, which makes it easier for context-dependent attackers to predict the result string by leveraging knowledge of random strings obtained in an earlier process with the same PID. 1.8.7_p352 is in tree, is it ok to go stable?
CVE-2011-2686 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-2686): Ruby before 1.8.7-p352 does not reset the random seed upon forking, which makes it easier for context-dependent attackers to predict the values of random numbers by leveraging knowledge of the number sequence obtained in a different child process, a related issue to CVE-2003-0900. NOTE: this issue exists because of a regression during Ruby 1.8.6 development.
(In reply to comment #0) > > 1.8.7_p352 is in tree, is it ok to go stable? Should be fine. Please test and mark stable: =dev-lang/ruby-1.8.7_p352
amd64 ok
amd64 done. Thanks Agostino
better late than never ditto
ppc/ppc64 stable
Stable for HPPA.
x86 stable.
arm stable
alpha/ia64/s390/sh/sparc stable
Thanks, everyone. GLSA Vote: no.
NO too. Closing.