summaryrefslogtreecommitdiff
path: root/projects
diff options
context:
space:
mode:
authorSteve Holme <steve_holme@hotmail.com>2015-07-26 19:50:03 +0100
committerSteve Holme <steve_holme@hotmail.com>2015-07-27 00:48:53 +0100
commit7db03e5c2131ae76cc5c2ca19dd93c10d026ac6c (patch)
treed19ff4c6efc4b67e8a904097395e6e020a855a8d /projects
parenta728225a9244276f1a3a6f3cee2e4410ae8259da (diff)
downloadcurl-7db03e5c2131ae76cc5c2ca19dd93c10d026ac6c.tar.gz
README: Corrected formatting for 'Legacy Windows and SSL' section
...as well as some wording.
Diffstat (limited to 'projects')
-rw-r--r--projects/README13
1 files changed, 7 insertions, 6 deletions
diff --git a/projects/README b/projects/README
index 27095380a..c727a3edd 100644
--- a/projects/README
+++ b/projects/README
@@ -112,12 +112,13 @@ Notes
Legacy Windows and SSL
======================
-Some of the project configurations use as an SSL backend WinSSL (Windows SSPI,
-more specifically Schannel), the native SSL library that comes with the Windows
-OS. WinSSL in Windows <= XP is not able 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 like OpenSSL.
+
+ 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.
TODO
====