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 aacc75fdf00e060e43ba744d149a40388b006221..7b7f4dce91899b78a65d405eecc296be27ac2d4c 100644 (file)
--- 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