git/list[1] front-page[2] threads[3] people[4] search[5] about
 

js/mingw-http-ssl, was Re: What's cooking in git.git (Oct 2018, #05; Fri, 26)

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Oct 26, 2018, 12:09 UTC
Message-ID
<nycvar.QRO.7.76.6.1810261407030.4546@tvgsbejvaqbjf.bet>
In-Reply-To
<xmqqo9bhcf89.fsf@gitster-ct.c.googlers.com>
Hi Junio,
On Fri, 26 Oct 2018, Junio C Hamano wrote:
Show 11 quoted lines
> * 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'.

Thanks, Dscho

Previous: Junio C HamanoNext: Junio C Hamano
Message 2 of 13 in “What's cooking in git.git (Oct 2018, #05; Fri, 26)”
  1. Junio C HamanoOct 26, 2018
  2. js/mingw-http-ssl, was Re: What's cooking in git.git (Oct 2018, #05; Fri, 26)Johannes Schindelin, Oct 26, 2018
  3. Junio C HamanoOct 26, 2018
  4. Johannes SchindelinOct 29, 2018
  5. Junio C HamanoOct 30, 2018
  6. Eric SunshineOct 30, 2018
  7. Junio C HamanoOct 30, 2018
  8. Kaartic SivaraamOct 30, 2018
  9. Johannes SchindelinOct 30, 2018
  10. Stefan BellerOct 26, 2018
  11. Junio C HamanoOct 27, 2018
  12. Taylor BlauOct 27, 2018
  13. Jeff KingOct 27, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.