WARNING! Gitlab maintenance operation scheduled for Monday, 20 April between 12:00 and 14:00 (CET). During this time window, short service interruptions (less than 5 minutes) may occur. Thank you in advance for your understanding.

Commit 6842afbf authored Jun 20, 2015 by Jay Satiro

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>

parent ea1eec8e

docs/INSTALL

+9 −0

Original line number	Original line	Diff line number	Diff line
	@@ -471,6 +471,15 @@ Win32
	add '-DCURL_STATICLIB' to your CFLAGS. Otherwise the linker will look for		add '-DCURL_STATICLIB' to your CFLAGS. Otherwise the linker will look for
	dynamic import symbols.		dynamic import symbols.

			Legacy Windows and SSL
			----------------------
			WinSSL (Windows SSPI, more specifically Schannel), is 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.

	Apple iOS and Mac OS X		Apple iOS and Mac OS X
	======================		======================

projects/README

+9 −0

Original line number	Original line	Diff line number	Diff line
	@@ -110,6 +110,15 @@ Notes
	stored in the git repositoty) will need to be modified rather than the		stored in the git repositoty) will need to be modified rather than the
	generated project files that Visual Studio uses.		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		TODO
	====		====

winbuild/BUILD.WINDOWS.txt

+11 −2

Original line number	Original line	Diff line number	Diff line
	Building with Visual C++, prerequises		Building with Visual C++, prerequisites
	=====================================		=======================================

	This document describes how to compile, build and install curl and libcurl		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		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		already built but not with that option, or if the option was specified
	differently, you must destroy the build directory containing the configuration		differently, you must destroy the build directory containing the configuration
	so that nmake can build it from scratch.		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.