Skip to content

G
git2
Commit 02ab4841 by Edward Thomson
Options

threading: clarify openssl default vs mbedtls

parent 358a3b9c
Showing with 5 additions and 4 deletions
docs/threading.md
...@@ -58,10 +58,11 @@ general case still affects you if you use ssh. ...@@ -58,10 +58,11 @@ general case still affects you if you use ssh.
General Case General Case
------------ ------------
If there are no applicable TLS implementations (currently only libgit2 will default to OpenSSL for HTTPS transport (except on Windows and
SecureTransport and mbedTLS), libgit2 defaults to OpenSSL in order to use HTTPS as a transport. macOS, as mentioned above). On any system, mbedTLS _may_ be optionally
OpenSSL is thread-safe starting at version 1.1.0. If your copy of libgit2 is enabled as the security provider. OpenSSL is thread-safe starting at
linked against that version, you do not need to take any further steps. version 1.1.0. If your copy of libgit2 is linked against that version,
you do not need to take any further steps.
Older versions of OpenSSL are made to be thread-implementation agnostic, and the Older versions of OpenSSL are made to be thread-implementation agnostic, and the
users of the library must set which locking function it should use. libgit2 users of the library must set which locking function it should use. libgit2
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment