Have code and doc consistent.

The SSLRandomSeed  builtin, uses 128 bytes of stack, not 1kb of scoreboard data.
(r1832346 in trunk)

See PR 54752

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1832347 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/mod/mod_ssl.xml b/docs/manual/mod/mod_ssl.xml
index a2a41042b7a0e6b2450c9678f1ba4d813b4ef46d..cae5ae69e4f406460e1b105eb78b0c3f4ddd4fe3 100644 (file)
--- a/docs/manual/mod/mod_ssl.xml
+++ b/docs/manual/mod/mod_ssl.xml
@@ -389,8 +389,8 @@ The following <em>source</em> variants are available:</p>
     <p> This is the always available builtin seeding source. Its usage
     consumes minimum CPU cycles under runtime and hence can be always used
     without drawbacks. The source used for seeding the PRNG contains of the
-    current time, the current process id and (when applicable) a randomly
-    chosen 1KB extract of the inter-process scoreboard structure of Apache.
+    current time, the current process id and a randomly
+    chosen 128 bytes extract of the stack.
     The drawback is that this is not really a strong source and at startup
     time (where the scoreboard is still not available) this source just
     produces a few bytes of entropy. So you should always, at least for the