From: Daniel Stenberg <daniel@haxx.se>
Date: Sun, 8 May 2016 13:48:26 +0000 (+0200)
Subject: libcurl-thread.3: openssl 1.1.0 is safe, and so is boringssl
X-Git-Tag: curl-7_49_0~25
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=5bf5f6ebfcede78ef7c2b16daa41c4b7ba266087;p=thirdparty%2Fcurl.git

libcurl-thread.3: openssl 1.1.0 is safe, and so is boringssl
---

diff --git a/docs/libcurl/libcurl-thread.3 b/docs/libcurl/libcurl-thread.3
index aacc75fdf0..7b7f4dce91 100644
--- a/docs/libcurl/libcurl-thread.3
+++ b/docs/libcurl/libcurl-thread.3
@@ -44,6 +44,8 @@ or two functions to allow it to function properly:
 https://www.openssl.org/docs/crypto/threads.html#DESCRIPTION
 
 https://curl.haxx.se/libcurl/c/opensslthreadlock.html
+
+For OpenSSL versions starting with 1.1.0, no particular action is required.
 .IP GnuTLS
 http://gnutls.org/manual/html_node/Thread-safety.html
 .IP NSS
@@ -60,6 +62,8 @@ The engine is used by libcurl in a way that is fully thread-safe.
 The engine is used by libcurl in a way that is fully thread-safe.
 .IP wolfSSL
 The engine is used by libcurl in a way that is fully thread-safe.
+.IP BoringSSL
+The engine is used by libcurl in a way that is fully thread-safe.
 .SH "Other areas of caution"
 .IP Signals
 Signals are used for timing out name resolves (during DNS lookup) - when built