The branch master has been updated via a08e2bf548507443ce9a020dd4cc68a57c27a8b7 (commit) from c339c702f6043fabd09904044f967e71629bc40f (commit)
- Log ----------------------------------------------------------------- commit a08e2bf548507443ce9a020dd4cc68a57c27a8b7 Author: Dr. Matthias St. Pierre <matthias.st.pie...@ncp-e.com> Date: Wed Mar 4 23:13:24 2020 +0100 doc: slightly reformulate 'openssl(1)/Random State Options' section Reviewed-by: Tomas Mraz <tm...@fedoraproject.org> (Merged from https://github.com/openssl/openssl/pull/11252) ----------------------------------------------------------------------- Summary of changes: doc/man1/openssl.pod | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/man1/openssl.pod b/doc/man1/openssl.pod index 2f56ab7592..ff66846337 100644 --- a/doc/man1/openssl.pod +++ b/doc/man1/openssl.pod @@ -727,11 +727,11 @@ Do not use the default store. =head2 Random State Options -Prior to OpenSSL 3.0, it was common for applications to store information +Prior to OpenSSL 1.1.1, it was common for applications to store information about the state of the random-number generator in a file that was loaded at startup and rewritten upon exit. On modern operating systems, this is -generally no longer necessary as OpenSSL will seed itself from the -appropriate CPU flags, device files, and so on. These flags are still +generally no longer necessary as OpenSSL will seed itself from a trusted +entropy source provided by the operating system. These flags are still supported for special platforms or circumstances that might require them. It is generally an error to use the same seed file more than once and