aboutsummaryrefslogtreecommitdiff
path: root/projects/README
diff options
context:
space:
mode:
authorSteve Holme <steve_holme@hotmail.com>2019-04-09 20:34:10 +0100
committerSteve Holme <steve_holme@hotmail.com>2019-04-10 22:05:38 +0100
commit37c43bf70c43ae02d36a774e511dc9fa20f64980 (patch)
treeb0083be98a31363ffc5f2deee50f2c2891c0218b /projects/README
parentff1cb97517af709e6fb3a7623582a3859cb44a85 (diff)
README: Schannel, stop calling it "winssl"
Stick to "Schannel" everywhere - follow up to 180501cb.
Diffstat (limited to 'projects/README')
-rw-r--r--projects/README12
1 files changed, 6 insertions, 6 deletions
diff --git a/projects/README b/projects/README
index be3e1e0e3..62b998656 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.