about summary refs log tree commit homepage
path: root/KNOWN_ISSUES
diff options
context:
space:
mode:
authorEric Wong <normalperson@yhbt.net>2011-04-26 16:04:19 -0700
committerEric Wong <normalperson@yhbt.net>2011-04-26 16:04:19 -0700
commit1b3befbadb99c83c24109f68b719276f0051c7fb (patch)
treee75003b5d1abeb28b3b6a4ad8dc51dfb807d06c7 /KNOWN_ISSUES
parent34f7dbd1b7e087bc8c86029496fd8daa7dc58441 (diff)
downloadunicorn-1b3befbadb99c83c24109f68b719276f0051c7fb.tar.gz
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.
Diffstat (limited to 'KNOWN_ISSUES')
-rw-r--r--KNOWN_ISSUES4
1 files changed, 2 insertions, 2 deletions
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