summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNick Zitzmann <nick@chronosnet.com>2013-01-23 17:41:23 -0700
committerDaniel Stenberg <daniel@haxx.se>2013-01-28 22:33:11 +0100
commit23a47ef01b22a1eb3e6a1005631f76a4f93d89f5 (patch)
treef89148f405fa8e231342750782a40dc1c1064f7f
parent38ec16d671d5eeb0be2d01fdf4c931cf54a9ec9c (diff)
downloadgnurl-23a47ef01b22a1eb3e6a1005631f76a4f93d89f5.tar.gz
gnurl-23a47ef01b22a1eb3e6a1005631f76a4f93d89f5.tar.bz2
gnurl-23a47ef01b22a1eb3e6a1005631f76a4f93d89f5.zip
FAQ: "Darwinssl" is AKA "Secure Transport" and supports NTLM
-rw-r--r--docs/FAQ11
1 files changed, 6 insertions, 5 deletions
diff --git a/docs/FAQ b/docs/FAQ
index b820af24e..4a2905196 100644
--- a/docs/FAQ
+++ b/docs/FAQ
@@ -424,9 +424,10 @@ FAQ
backends.
curl can be built to use one of the following SSL alternatives: OpenSSL,
- GnuTLS, yassl, NSS, PolarSSL, axTLS, Darwinssl, schannel (native Windows) or
- qssl. They all have their pros and cons, and we try to maintain a comparison
- of them here: http://curl.haxx.se/docs/ssl-compared.html
+ GnuTLS, yassl, NSS, PolarSSL, axTLS, Secure Transport (native iOS/OS X),
+ schannel (native Windows) or qssl (native IBM i). They all have their pros
+ 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?
@@ -912,8 +913,8 @@ FAQ
4.9 Curl can't authenticate to the server that requires NTLM?
- NTLM support requires OpenSSL, GnuTLS, NSS or Microsoft Windows libraries at
- build-time to provide this functionality.
+ NTLM support requires OpenSSL, GnuTLS, NSS, Secure Transport, or Microsoft
+ Windows libraries at build-time to provide this functionality.
NTLM is a Microsoft proprietary protocol. Proprietary formats are evil. You
should not use such ones.