From: Steve Holme Date: Tue, 9 Apr 2019 19:34:10 +0000 (+0100) Subject: README: Schannel, stop calling it "winssl" X-Git-Tag: curl-7_65_0~174 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=37c43bf70c43ae02d36a774e511dc9fa20f64980;p=thirdparty%2Fcurl.git README: Schannel, stop calling it "winssl" Stick to "Schannel" everywhere - follow up to 180501cb. --- diff --git a/projects/README b/projects/README index be3e1e0e35..62b9986568 100644 --- a/projects/README +++ b/projects/README @@ -151,9 +151,9 @@ Notes Legacy Windows and SSL ====================== - Some of the project configurations allow the use of WinSSL (specifically - Schannel from Windows SSPI), the native SSL library in Windows. However, - WinSSL in Windows <= XP is unable to connect to servers that no longer - support the legacy handshakes and algorithms used by those versions. If - you will be using curl in one of those earlier versions of Windows you - should choose another SSL backend such as OpenSSL. + Some of the project configurations allow the use of Schannel, the native + SSL library in Windows which forms part of Windows SSPI. However, Schannel + in Windows <= XP is unable to connect to servers that no longer support the + legacy handshakes and algorithms used by those versions. If you will be + using curl in one of those earlier versions of Windows you should choose + another SSL backend such as OpenSSL.