]> granicus.if.org Git - curl/commit
ntlm: use strict order for SSL backend #if branches
authorViktor Szakats <vszakats@users.noreply.github.com>
Wed, 30 Aug 2017 21:10:38 +0000 (21:10 +0000)
committerViktor Szakats <vszakats@users.noreply.github.com>
Fri, 22 Sep 2017 19:01:28 +0000 (19:01 +0000)
commit6f86022df26243cc8a035fe8b4c89033b6a04bc0
treea18d9ba9de9668fd3034e62a2a66908d835b3ed3
parent7c52b12dd4721d4c5591cefa078d256331e56999
ntlm: use strict order for SSL backend #if branches

With the recently introduced MultiSSL support multiple SSL backends
can be compiled into cURL That means that now the order of the SSL

One option would be to use the same SSL backend as was configured
via `curl_global_sslset()`, however, NTLMv2 support would appear
to be available only with some SSL backends. For example, when
eb88d778e (ntlm: Use Windows Crypt API, 2014-12-02) introduced
support for NTLMv1 using Windows' Crypt API, it specifically did
*not* introduce NTLMv2 support using Crypt API at the same time.

So let's select one specific SSL backend for NTLM support when
compiled with multiple SSL backends, using a priority order such
that we support NTLMv2 even if only one compiled-in SSL backend can
be used for that.

Ref: https://github.com/curl/curl/pull/1848
lib/curl_ntlm_core.c
lib/http_ntlm.c
lib/vauth/ntlm.c
lib/vtls/vtls.h