X-Git-Url: https://git.openssl.org/gitweb/?p=openssl.git;a=blobdiff_plain;f=doc%2Fcrypto%2FOPENSSL_config.pod;h=77061a00ce72e6ae92ecfc1bea10c30122c00a29;hp=91d61f3f519b5a6bca0aa6abecd851c8c5344476;hb=cbf6959fe8ff51730a397ea426075d547ec5d7a8;hpb=abdd677125f3a9e3082f8c5692203590fdb9b860 diff --git a/doc/crypto/OPENSSL_config.pod b/doc/crypto/OPENSSL_config.pod index 91d61f3f51..77061a00ce 100644 --- a/doc/crypto/OPENSSL_config.pod +++ b/doc/crypto/OPENSSL_config.pod @@ -23,9 +23,6 @@ Multiple calls have no effect. OPENSSL_no_config() disables configuration. If called before OPENSSL_config() no configuration takes place. -Applications should free up configuration at application closedown by calling -CONF_modules_free(). - If the application is built with B defined, then a call to OpenSSL_add_all_algorithms() will implicitly call OPENSSL_config() first. @@ -42,9 +39,7 @@ Applications should instead call CONF_modules_load() during initialization (that is before starting any threads). There are several reasons why calling the OpenSSL configuration routines is -advisable. For example new ENGINE functionality was added to OpenSSL 0.9.7. -In OpenSSL 0.9.7 control functions can be supported by ENGINEs, this can be -used (among other things) to load dynamic ENGINEs from shared libraries (DSOs). +advisable. For example, to load dynamic ENGINEs from shared libraries (DSOs). However very few applications currently support the control interface and so very few can load and use dynamic ENGINEs. Equally in future more sophisticated ENGINEs will require certain control operations to customize them. If an @@ -58,12 +53,12 @@ Neither OPENSSL_config() nor OPENSSL_no_config() return a value. =head1 SEE ALSO -L, -L, -L +L, +L =head1 HISTORY -OPENSSL_config() and OPENSSL_no_config() first appeared in OpenSSL 0.9.7 +The OPENSSL_no_config() and OPENSSL_config() functions were +deprecated in OpenSSL 1.1.0 by OPENSSL_init_crypto(). =cut