From 1b3befbadb99c83c24109f68b719276f0051c7fb Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Tue, 26 Apr 2011 16:04:19 -0700 Subject: unicorn 3.6.1 - fix OpenSSL PRNG workaround Our attempt in 3.6.0 to workaround a problem with the OpenSSL PRNG actually made the problem worse. This release corrects the workaround to properly reseed the OpenSSL PRNG after forking. --- GIT-VERSION-GEN | 2 +- KNOWN_ISSUES | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/GIT-VERSION-GEN b/GIT-VERSION-GEN index 66f38a3..f5fd878 100755 --- a/GIT-VERSION-GEN +++ b/GIT-VERSION-GEN @@ -1,7 +1,7 @@ #!/bin/sh GVF=GIT-VERSION-FILE -DEF_VER=v3.6.0.GIT +DEF_VER=v3.6.1.GIT LF=' ' diff --git a/KNOWN_ISSUES b/KNOWN_ISSUES index 4a6e490..2bd4151 100644 --- a/KNOWN_ISSUES +++ b/KNOWN_ISSUES @@ -5,13 +5,13 @@ acceptable solution. Those issues are documented here. * PRNGs (pseudo-random number generators) loaded before forking (e.g. "preload_app true") may need to have their internal state - reset in the after_fork hook. Starting with \Unicorn 3.6.0, we + reset in the after_fork hook. Starting with \Unicorn 3.6.1, we have builtin workarounds for Kernel#rand and OpenSSL::Random users, but applications may use other PRNGs. * Under some versions of Ruby 1.8, it is necessary to call +srand+ in an after_fork hook to get correct random number generation. We have a builtin - workaround for this starting with \Unicorn 3.6.0 + workaround for this starting with \Unicorn 3.6.1 See http://redmine.ruby-lang.org/issues/show/4338 -- cgit v1.2.3-24-ge0c7