aboutsummaryrefslogtreecommitdiff
path: root/projects
diff options
context:
space:
mode:
authorJay Satiro <raysatiro@yahoo.com>2015-06-20 18:45:25 -0400
committerJay Satiro <raysatiro@yahoo.com>2015-06-20 18:45:25 -0400
commit6842afbf4498198766bf4ff6300a5f267fcbd361 (patch)
treef653edb67a38ace304f8ed81ef0962a13affe3df /projects
parentea1eec8ea88ade9137cdb6db422d00b273daef03 (diff)
INSTALL: Advise use of non-native SSL for Windows <= XP
Advise that WinSSL in versions <= XP will not be able to connect to servers that no longer support the legacy handshakes and algorithms used by those versions, and to use an alternate backend like OpenSSL instead. Bug: https://github.com/bagder/curl/issues/253 Reported-by: zenden2k <zenden2k@gmail.com>
Diffstat (limited to 'projects')
-rw-r--r--projects/README9
1 files changed, 9 insertions, 0 deletions
diff --git a/projects/README b/projects/README
index b45d78397..27095380a 100644
--- a/projects/README
+++ b/projects/README
@@ -110,6 +110,15 @@ Notes
stored in the git repositoty) will need to be modified rather than the
generated project files that Visual Studio uses.
+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.
+
TODO
====