I can't test NTLM here but I have a precompiled version of curl here that has the same features with OpenSSL. The only difference is, that it was compiled for mingw. So I guess this is a valid configuration with the automake build chain.

-----Ursprüngliche Nachricht-----
Von: curl-library [mailto:curl-library-bounces_at_cool.haxx.se] Im Auftrag von Sergei Nikulov via curl-library
Gesendet: Freitag, 26. Januar 2018 11:07
An: libcurl development <curl-library_at_cool.haxx.se>
Cc: Sergei Nikulov <sergey.nikulov_at_gmail.com>
Betreff: Re: Patch: CMake win32 enable SSPI with OpenSSL

2018-01-26 12:25 GMT+03:00 David Weisgerber <david.weisgerber_at_ms-gmbh.de>:
> Hi,
>
> this is a little patch that changes the CMake behaviour on Win32
> regarding SSPI with OpenSSL. It enables me to build curl with the
> following features on Win32 with Visual Studio 2015:
>
> curl 7.58.0 (Windows) libcurl/7.58.0 OpenSSL/1.0.2n zlib/1.2.11
> nghttp2/1.22.90
>
> Release-Date: 2018-01-24
>
> Protocols: http https
>
> Features: AsynchDNS IPv6 Largefile SSPI Kerberos SPNEGO NTLM SSL libz
> HTTP2 HTTPS-proxy
>
>
>
> Without the patch, SSPI, Kerberos and SPNEGO were disabled when not
> using WinSSL.
>
>
>
> Best regards,
>
> David

When it builds it's really cool. But how does curl work after those changes?

I suspect, NTLM backend start working through OpenSSL, despite WinCrypt.

Any testing results for all involved protocols?

>
> -------------------------------------------------------------------
> Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
> Etiquette: https://curl.haxx.se/mail/etiquette.html

--
Best Regards,
Sergei Nikulov
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette:   https://curl.haxx.se/mail/etiquette.html
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette:   https://curl.haxx.se/mail/etiquette.html