1
0
mirror of https://github.com/moparisthebest/curl synced 2024-08-13 17:03:50 -04:00

FAQ: "Darwinssl" is AKA "Secure Transport" and supports NTLM

This commit is contained in:
Nick Zitzmann 2013-01-23 17:41:23 -07:00 committed by Daniel Stenberg
parent 38ec16d671
commit 23a47ef01b

View File

@ -424,9 +424,10 @@ FAQ
backends. backends.
curl can be built to use one of the following SSL alternatives: OpenSSL, curl can be built to use one of the following SSL alternatives: OpenSSL,
GnuTLS, yassl, NSS, PolarSSL, axTLS, Darwinssl, schannel (native Windows) or GnuTLS, yassl, NSS, PolarSSL, axTLS, Secure Transport (native iOS/OS X),
qssl. They all have their pros and cons, and we try to maintain a comparison schannel (native Windows) or qssl (native IBM i). They all have their pros
of them here: http://curl.haxx.se/docs/ssl-compared.html and cons, and we try to maintain a comparison of them here:
http://curl.haxx.se/docs/ssl-compared.html
2.3 Where can I find a copy of LIBEAY32.DLL? 2.3 Where can I find a copy of LIBEAY32.DLL?
@ -912,8 +913,8 @@ FAQ
4.9 Curl can't authenticate to the server that requires NTLM? 4.9 Curl can't authenticate to the server that requires NTLM?
NTLM support requires OpenSSL, GnuTLS, NSS or Microsoft Windows libraries at NTLM support requires OpenSSL, GnuTLS, NSS, Secure Transport, or Microsoft
build-time to provide this functionality. Windows libraries at build-time to provide this functionality.
NTLM is a Microsoft proprietary protocol. Proprietary formats are evil. You NTLM is a Microsoft proprietary protocol. Proprietary formats are evil. You
should not use such ones. should not use such ones.