From: Christophe Jaillet Date: Sun, 27 May 2018 20:19:50 +0000 (+0000) Subject: Have code and doc consistent. X-Git-Tag: 2.4.34~167 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=c4b3a7a0f5275a25848ef21eb967141a00e08b55;p=apache 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 a2a41042b7..cae5ae69e4 100644 --- a/docs/manual/mod/mod_ssl.xml +++ b/docs/manual/mod/mod_ssl.xml @@ -389,8 +389,8 @@ The following source variants are available:

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