Skip to content

Commit

Permalink
Docs for OpenSSL_init_crypto: there is no way to specify another file
Browse files Browse the repository at this point in the history
The documentation erroneously stated that one can change the default
configuration file name.

Fixes #5939

Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from #5941)
  • Loading branch information
levitte committed Apr 13, 2018
1 parent b4c1950 commit 0320e8e
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions doc/man3/OPENSSL_init_crypto.pod
Expand Up @@ -197,10 +197,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
Expand Down

0 comments on commit 0320e8e

Please sign in to comment.