js/mingw-http-ssl, was Re: What's cooking in git.git (Oct 2018, #05; Fri, 26)
- Date: Fri, 26 Oct 2018 14:09:52 +0200 (DST)
- From: Johannes Schindelin <Johannes.Schindelin@xxxxxx>
- Subject: js/mingw-http-ssl, was Re: What's cooking in git.git (Oct 2018, #05; Fri, 26)
On Fri, 26 Oct 2018, Junio C Hamano wrote:
> * js/mingw-http-ssl (2018-10-26) 3 commits
> (merged to 'next' on 2018-10-26 at 318e82e101)
> + http: when using Secure Channel, ignore sslCAInfo by default
> + http: add support for disabling SSL revocation checks in cURL
> + http: add support for selecting SSL backends at runtime
> (this branch is used by jc/http-curlver-warnings.)
> On Windows with recent enough cURL library, the configuration
> variable http.sslBackend can be used to choose between OpenSSL and
> Secure Channel at runtime as the SSL backend while talking over
> the HTTPS protocol.
Just a quick clarification: the http.sslBackend feature is in no way
Windows-only. Sure, it was championed there, and sure, we had the first
multi-ssl-capable libcurl, but this feature applies to all libcurl
versions that are built with multiple SSL/TLS backends.
The two patches on top are Windows-only, of course, as they really apply
only to the Secure Channel backend (which *is* Windows-only).
> Will merge to 'master'.