X-Git-Url: https://gitweb.dragonflybsd.org/~nant/dragonfly.git/blobdiff_plain/ec7d8cd6e0ae18eb78554384fd13c96b973f2250..7dc78669e8e5968f18ec562d7ad1e62046d248ba:/secure/lib/libcrypto/man/OPENSSL_config.3

diff --git a/secure/lib/libcrypto/man/OPENSSL_config.3 b/secure/lib/libcrypto/man/OPENSSL_config.3
index c9e00ee180..53022afead 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.25 (Pod::Simple 3.20)
+.\" Automatically generated by Pod::Man 2.27 (Pod::Simple 3.28)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -38,6 +38,8 @@
 .    ds PI \(*p
 .    ds L" ``
 .    ds R" ''
+.    ds C`
+.    ds C'
 'br\}
 .\"
 .\" Escape single quotes in literal strings from groff's Unicode transform.
@@ -48,17 +50,24 @@
 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
 .\" entries marked with X<> in POD.  Of course, you'll have to process the
 .\" output yourself in some meaningful fashion.
-.ie \nF \{\
-.    de IX
-.    tm Index:\\$1\t\\n%\t"\\$2"
+.\"
+.\" Avoid warning from groff about undefined register 'F'.
+.de IX
 ..
-.    nr % 0
-.    rr F
-.\}
-.el \{\
-.    de IX
+.nr rF 0
+.if \n(.g .if rF .nr rF 1
+.if (\n(rF:(\n(.g==0)) \{
+.    if \nF \{
+.        de IX
+.        tm Index:\\$1\t\\n%\t"\\$2"
 ..
+.        if !\nF==2 \{
+.            nr % 0
+.            nr F 2
+.        \}
+.    \}
 .\}
+.rr rF
 .\"
 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
 .\" Fear.  Run.  Save yourself.  No user-serviceable parts.
@@ -124,7 +133,7 @@
 .\" ========================================================================
 .\"
 .IX Title "OPENSSL_config 3"
-.TH OPENSSL_config 3 "2014-10-15" "1.0.1j" "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
@@ -143,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.