aboutsummaryrefslogtreecommitdiff
path: root/docs/libcurl/libcurl-thread.3
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2016-05-08 15:48:26 +0200
committerDaniel Stenberg <daniel@haxx.se>2016-05-08 15:48:26 +0200
commit5bf5f6ebfcede78ef7c2b16daa41c4b7ba266087 (patch)
treed9265aff4f1a07c5702044af82c8e182331a6969 /docs/libcurl/libcurl-thread.3
parentae8f6620726c51aaf69f92a846fae63e74c9fab2 (diff)
libcurl-thread.3: openssl 1.1.0 is safe, and so is boringssl
Diffstat (limited to 'docs/libcurl/libcurl-thread.3')
-rw-r--r--docs/libcurl/libcurl-thread.34
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/libcurl/libcurl-thread.3 b/docs/libcurl/libcurl-thread.3
index aacc75fdf..7b7f4dce9 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