[openssl-commits] [openssl] OpenSSL_1_1_0-stable update

Richard Levitte levitte at openssl.org
Fri Apr 13 08:26:56 UTC 2018

The branch OpenSSL_1_1_0-stable has been updated
       via  2a479a86bd5eca8792a75a08c836b405f3cef4d6 (commit)
      from  e7bc92bc782b995231dbf855970f206ebc65c75d (commit)

- Log -----------------------------------------------------------------
commit 2a479a86bd5eca8792a75a08c836b405f3cef4d6
Author: Richard Levitte <levitte at openssl.org>
Date:   Fri Apr 13 08:19:54 2018 +0200

    Docs for OpenSSL_init_crypto: there is no way to specify another file
    The documentation erroneously stated that one can change the default
    configuration file name.
    Fixes #5939
    Reviewed-by: Matt Caswell <matt at openssl.org>
    (Merged from https://github.com/openssl/openssl/pull/5941)
    (cherry picked from commit 0320e8e2869fb6cde4579375e65f6d576bbec95e)


Summary of changes:
 doc/crypto/OPENSSL_init_crypto.pod | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/crypto/OPENSSL_init_crypto.pod b/doc/crypto/OPENSSL_init_crypto.pod
index f0b3c8a..cb64705 100644
--- a/doc/crypto/OPENSSL_init_crypto.pod
+++ b/doc/crypto/OPENSSL_init_crypto.pod
@@ -190,10 +190,10 @@ resources should be freed at an earlier time, or under the circumstances
 described in the NOTES section below.
 The B<OPENSSL_INIT_LOAD_CONFIG> flag will load a default configuration
-file.  To specify a different file, an B<OPENSSL_INIT_SETTINGS> must
-be created and used. The routines
-OPENSSL_init_new() and OPENSSL_INIT_set_config_appname() can be used to
-allocate the object and set the application name, and then the
+file. For optional configuration file settings, an B<OPENSSL_INIT_SETTINGS>
+must be created and used.
+The routines OPENSSL_init_new() and OPENSSL_INIT_set_config_appname() can
+be used to allocate the object and set the application name, and then the
 object can be released with OPENSSL_INIT_free() when done.
 =head1 NOTES

More information about the openssl-commits mailing list