From: Richard Levitte Date: Fri, 13 Apr 2018 06:19:54 +0000 (+0200) Subject: Docs for OpenSSL_init_crypto: there is no way to specify another file X-Git-Tag: OpenSSL_1_1_0i~191 X-Git-Url: https://git.librecmc.org/?a=commitdiff_plain;h=2a479a86bd5eca8792a75a08c836b405f3cef4d6;p=oweals%2Fopenssl.git 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 (Merged from https://github.com/openssl/openssl/pull/5941) (cherry picked from commit 0320e8e2869fb6cde4579375e65f6d576bbec95e) --- diff --git a/doc/crypto/OPENSSL_init_crypto.pod b/doc/crypto/OPENSSL_init_crypto.pod index f0b3c8aa8d..cb647059a8 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 flag will load a default configuration -file. To specify a different file, an B 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 +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