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

This commit is contained in:
Daniel Stenberg 2016-05-08 15:48:26 +02:00
parent ae8f662072
commit 5bf5f6ebfc
1 changed files with 4 additions and 0 deletions

View File

@ -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