From: Nick Zitzmann <nick@chronosnet.com>
Date: Thu, 24 Jan 2013 00:41:23 +0000 (-0700)
Subject: FAQ: "Darwinssl" is AKA "Secure Transport" and supports NTLM
X-Git-Tag: curl-7_29_0~41
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=23a47ef01b22a1eb3e6a1005631f76a4f93d89f5;p=thirdparty%2Fcurl.git

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

diff --git a/docs/FAQ b/docs/FAQ
index b820af24e4..4a29051968 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.