summaryrefslogtreecommitdiffstats
path: root/doc/man7/RAND.pod
diff options
context:
space:
mode:
authorDr. Matthias St. Pierre <Matthias.St.Pierre@ncp-e.com>2018-03-30 01:07:00 +0200
committerDr. Matthias St. Pierre <Matthias.St.Pierre@ncp-e.com>2018-04-11 18:56:03 +0200
commitf7bef277eac05853224d33e67465147833c49108 (patch)
treeee1e5c706f6a88581a5ff4f35d2a2bd0b59ec0ce /doc/man7/RAND.pod
parent708a6a17592865590344eca541cbfccd472d7b45 (diff)
Minor corrections for the RAND_DRBG API documentation
- added some explaining text to a sentence that lost its context. - removed mention of per-ssl drbg - fix whitespace errors Reviewed-by: Rich Salz <rsalz@openssl.org> (Merged from https://github.com/openssl/openssl/pull/5804)
Diffstat (limited to 'doc/man7/RAND.pod')
-rw-r--r--doc/man7/RAND.pod4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/man7/RAND.pod b/doc/man7/RAND.pod
index 6ec7548972..578018feab 100644
--- a/doc/man7/RAND.pod
+++ b/doc/man7/RAND.pod
@@ -32,8 +32,8 @@ return value of L<RAND_bytes(3)> and don't take randomness for granted.
For long-term secrets, you can use L<RAND_priv_bytes(3)> instead.
This method does not provide 'better' randomness, it uses the same type of CSPRNG.
The intention behind using a dedicated CSPRNG exclusively for long-term secrets is
-that none of its output should be visible to an attacker (e.g used as salt value),
-in order to reveal as little information as possible about its internal state.
+that none of its output should be visible to an attacker (e.g used as salt value),
+in order to reveal as little information as possible about its internal state.
In the rare case where the default implementation does not satisfy your special
requirements, there are two options: