From: Neil Horman Date: Mon, 26 Jan 2026 16:41:23 +0000 (-0500) Subject: Update doc/man3/OPENSSL_init_crypto.pod X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=c91cf3a52f2c12e114bec6b78a4f4085fc40e94c;p=thirdparty%2Fopenssl.git Update doc/man3/OPENSSL_init_crypto.pod Co-authored-by: Matt Caswell Reviewed-by: Tomas Mraz Reviewed-by: Matt Caswell Reviewed-by: Paul Dale MergeDate: Tue Jan 27 20:43:01 2026 (Merged from https://github.com/openssl/openssl/pull/29648) --- diff --git a/doc/man3/OPENSSL_init_crypto.pod b/doc/man3/OPENSSL_init_crypto.pod index b3bfbde11a3..830ace5f7c0 100644 --- a/doc/man3/OPENSSL_init_crypto.pod +++ b/doc/man3/OPENSSL_init_crypto.pod @@ -138,13 +138,13 @@ OPENSSL_init_crypto(). For example: The OPENSSL_cleanup() function deinitialises OpenSSL (both libcrypto and libssl). All resources allocated by OpenSSL are freed. An application using the OpenSSL library may call this function to free library resources -prior to application exit. However its use is discouraged, as there are many +prior to application exit. Note that there are some use cases in which subordinate libraries may also use OpenSSL and may not be finished with their references to it at application exit time (for example, if a subordinate library attempts to free an OpenSSL resource from a library destructor, calling OPENSSL_cleanup() may result in crashes or other unexpected -behavior. Instead it is strongly recommended that OPENSSL_cleanup() not be -called, allowing the operating system to reap all library resources on process +behavior). If this is likely to be a problem then it is recommended that OPENSSL_cleanup() +not be called, allowing the operating system to reap all library resources on process exit. Note, this may, on some leak detection tools (like valgrind) result in