From 6842afbf4498198766bf4ff6300a5f267fcbd361 Mon Sep 17 00:00:00 2001 From: Jay Satiro Date: Sat, 20 Jun 2015 18:45:25 -0400 Subject: 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 --- winbuild/BUILD.WINDOWS.txt | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) (limited to 'winbuild/BUILD.WINDOWS.txt') diff --git a/winbuild/BUILD.WINDOWS.txt b/winbuild/BUILD.WINDOWS.txt index 600f73746..ed19e56c0 100644 --- a/winbuild/BUILD.WINDOWS.txt +++ b/winbuild/BUILD.WINDOWS.txt @@ -1,5 +1,5 @@ -Building with Visual C++, prerequises -===================================== +Building with Visual C++, prerequisites +======================================= This document describes how to compile, build and install curl and libcurl from sources using the Visual C++ build tool. To build with VC++, you will @@ -87,3 +87,12 @@ therefore rarely tested. When passing RTLIBCFG for a configuration that was already built but not with that option, or if the option was specified differently, you must destroy the build directory containing the configuration so that nmake can build it from scratch. + +Legacy Windows and SSL +====================== +When you build curl using the build files in this directory the default SSL +backend will be 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. -- cgit v1.2.1