From 9d4e2f891b06c95e8c784be0df4572e2a23f9699 Mon Sep 17 00:00:00 2001 From: "Dr. Stephen Henson" Date: Tue, 2 Mar 2004 13:33:52 +0000 Subject: [PATCH] More configuration docs. --- doc/crypto/OPENSSL_config.pod | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/doc/crypto/OPENSSL_config.pod b/doc/crypto/OPENSSL_config.pod index 18da16f3c3..16600620cc 100644 --- a/doc/crypto/OPENSSL_config.pod +++ b/doc/crypto/OPENSSL_config.pod @@ -2,7 +2,7 @@ =head1 NAME -OPENSSL_config, OPENSSL_no_config - minimal OpenSSL configuration +OPENSSL_config, OPENSSL_no_config - simple OpenSSL configuration functions =head1 SYNOPSIS @@ -32,7 +32,8 @@ and some new functionality can be supported automatically. It is also possible to automatically call OPENSSL_config() when an application calls OPENSSL_add_all_algorithms() by compiling an application with the -preprocessor symbol B #define'd. +preprocessor symbol B #define'd. In this way configuration +can be added without source changes. The environment variable B can be set to specify the location of the configuration file. @@ -51,6 +52,9 @@ application calls OPENSSL_config() it doesn't need to know or care about ENGINE control operations because they can be performed by editing a configuration file. +Applications should free up configuration at application closedown by calling +CONF_modules_free(). + =head1 RESTRICTIONS The OPENSSL_config() function is designed to be a very simple "call it and @@ -59,7 +63,7 @@ all errors silently and it can only load from the standard configuration file location for example. It is however B better than nothing. Applications which need finer -control over the configuration functionality should use the configuration +control over their configuration functionality should use the configuration functions such as CONF_load_modules() directly. =head1 RETURN VALUES @@ -68,7 +72,8 @@ Neither OPENSSL_config() nor OPENSSL_no_config() return a value. =head1 SEE ALSO -L +L, L, +L =head1 HISTORY -- 2.25.1