From c216179af4c6d9bd69e7f83aa3975ab1a6ed44df Mon Sep 17 00:00:00 2001 From: Marc Hoersken Date: Sat, 4 Jan 2014 14:33:27 +0100 Subject: docs: primarily refer to schannel as WinSSL --- docs/FAQ | 2 +- docs/FEATURES | 4 ++-- docs/KNOWN_BUGS | 4 ++-- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/FAQ b/docs/FAQ index b6f8958af..3704f0562 100644 --- a/docs/FAQ +++ b/docs/FAQ @@ -422,7 +422,7 @@ FAQ curl can be built to use one of the following SSL alternatives: OpenSSL, GnuTLS, yassl, NSS, PolarSSL, axTLS, Secure Transport (native iOS/OS X), - schannel (native Windows) or qssl (native IBM i). They all have their pros + WinSSL (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 diff --git a/docs/FEATURES b/docs/FEATURES index 14d7e78dd..0221ce35e 100644 --- a/docs/FEATURES +++ b/docs/FEATURES @@ -176,14 +176,14 @@ IMAPS (*1) FOOTNOTES ========= - *1 = requires OpenSSL, GnuTLS, NSS, yassl, axTLS, PolarSSL, schannel (native + *1 = requires OpenSSL, GnuTLS, NSS, yassl, axTLS, PolarSSL, WinSSL (native Windows), Secure Transport (native iOS/OS X) or qssl (native IBM i) *2 = requires OpenLDAP *3 = requires a GSSAPI-compliant library, such as Heimdal or similar *4 = requires FBopenssl *5 = requires a krb4 library, such as the MIT one or similar *6 = requires c-ares - *7 = requires OpenSSL, NSS, qssl, schannel or Secure Transport; GnuTLS, for + *7 = requires OpenSSL, NSS, qssl, WinSSL or Secure Transport; GnuTLS, for example, only supports SSLv3 and TLSv1 *8 = requires libssh2 *9 = requires OpenSSL, GnuTLS, NSS, yassl, Secure Transport or SSPI (native diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS index e838fefdc..d167ab34b 100644 --- a/docs/KNOWN_BUGS +++ b/docs/KNOWN_BUGS @@ -69,12 +69,12 @@ may have been fixed since this was written! option as for all other operating systems. 75. NTLM authentication involving unicode user name or password only works - properly if built with UNICODE defined together with the schannel/winssl + properly if built with UNICODE defined together with the WinSSL/schannel backend. The original problem was mentioned in: http://curl.haxx.se/mail/lib-2009-10/0024.html http://curl.haxx.se/bug/view.cgi?id=896 - The schannel version verified to work as mentioned in + The WinSSL/schannel version verified to work as mentioned in http://curl.haxx.se/mail/lib-2012-07/0073.html 73. if a connection is made to a FTP server but the server then just never -- cgit v1.2.3