summaryrefslogtreecommitdiffstats
path: root/secure/lib/libcrypto/man/OPENSSL_config.3
diff options
context:
space:
mode:
Diffstat (limited to 'secure/lib/libcrypto/man/OPENSSL_config.3')
-rw-r--r--secure/lib/libcrypto/man/OPENSSL_config.335
1 files changed, 14 insertions, 21 deletions
diff --git a/secure/lib/libcrypto/man/OPENSSL_config.3 b/secure/lib/libcrypto/man/OPENSSL_config.3
index 443b9a0..f34f3e8 100644
--- a/secure/lib/libcrypto/man/OPENSSL_config.3
+++ b/secure/lib/libcrypto/man/OPENSSL_config.3
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28)
+.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.30)
.\"
.\" Standard preamble:
.\" ========================================================================
@@ -133,7 +133,7 @@
.\" ========================================================================
.\"
.IX Title "OPENSSL_config 3"
-.TH OPENSSL_config 3 "2015-01-15" "1.0.1l" "OpenSSL"
+.TH OPENSSL_config 3 "2015-07-09" "1.0.1p" "OpenSSL"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@@ -152,30 +152,23 @@ OPENSSL_config, OPENSSL_no_config \- simple OpenSSL configuration functions
.IX Header "DESCRIPTION"
\&\fIOPENSSL_config()\fR configures OpenSSL using the standard \fBopenssl.cnf\fR
configuration file name using \fBconfig_name\fR. If \fBconfig_name\fR is \s-1NULL\s0 then
-the default name \fBopenssl_conf\fR will be used. Any errors are ignored. Further
-calls to \fIOPENSSL_config()\fR will have no effect. The configuration file format
-is documented in the \fIconf\fR\|(5) manual page.
+the file specified in the environment variable \fB\s-1OPENSSL_CONF\s0\fR will be used,
+and if that is not set then a system default location is used.
+Errors are silently ignored.
+Multiple calls have no effect.
.PP
\&\fIOPENSSL_no_config()\fR disables configuration. If called before \fIOPENSSL_config()\fR
no configuration takes place.
.SH "NOTES"
.IX Header "NOTES"
-It is \fBstrongly\fR recommended that \fBall\fR new applications call \fIOPENSSL_config()\fR
-or the more sophisticated functions such as \fICONF_modules_load()\fR during
-initialization (that is before starting any threads). By doing this
-an application does not need to keep track of all configuration options
-and some new functionality can be supported automatically.
-.PP
-It is also possible to automatically call \fIOPENSSL_config()\fR when an application
-calls \fIOPENSSL_add_all_algorithms()\fR by compiling an application with the
-preprocessor symbol \fB\s-1OPENSSL_LOAD_CONF\s0\fR #define'd. In this way configuration
-can be added without source changes.
-.PP
-The environment variable \fB\s-1OPENSSL_CONF\s0\fR can be set to specify the location
-of the configuration file.
-.PP
-Currently \s-1ASN1\s0 OBJECTs and \s-1ENGINE\s0 configuration can be performed future
-versions of OpenSSL will add new configuration options.
+The \fIOPENSSL_config()\fR function is designed to be a very simple \*(L"call it and
+forget it\*(R" function.
+It is however \fBmuch\fR better than nothing. Applications which need finer
+control over their configuration functionality should use the configuration
+functions such as \fICONF_modules_load()\fR directly. This function is deprecated
+and its use should be avoided.
+Applications should instead call \fICONF_modules_load()\fR during
+initialization (that is before starting any threads).
.PP
There are several reasons why calling the OpenSSL configuration routines is
advisable. For example new \s-1ENGINE\s0 functionality was added to OpenSSL 0.9.7.
OpenPOWER on IntegriCloud