From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: js/mingw-http-ssl, was Re: What's cooking in git.git (Oct 2018, #05; Fri, 26)
Date: Fri, 26 Oct 2018 22:19:41 +0900 [thread overview]
Message-ID: <xmqqftwsdevm.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1810261407030.4546@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Fri, 26 Oct 2018 14:09:52 +0200 (DST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Hi Junio,
>
> 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.
Yeah, but "http.sslBackend can be used to choose betnween OpenSSL
and Scure Channel" applies only to Windows (especially the "between
A and B" part, when B is Windows only), right? I had a hard time
coming up with a phrasing to summarize what the immediate merit
users would get from the topic in a simple paragraph.
> The two patches on top are Windows-only, of course, as they really apply
> only to the Secure Channel backend (which *is* Windows-only).
Yes, that is why the summary for the topic as a whole focuses on
Windows, as that is the primary audience who would benefit from the
topic.
next prev parent reply other threads:[~2018-10-26 13:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 7:57 What's cooking in git.git (Oct 2018, #05; Fri, 26) Junio C Hamano
2018-10-26 12:09 ` js/mingw-http-ssl, was " Johannes Schindelin
2018-10-26 13:19 ` Junio C Hamano [this message]
2018-10-29 13:22 ` Johannes Schindelin
2018-10-30 2:09 ` Junio C Hamano
2018-10-30 2:22 ` Eric Sunshine
2018-10-30 5:37 ` Junio C Hamano
2018-10-30 5:49 ` Kaartic Sivaraam
2018-10-30 10:16 ` Johannes Schindelin
2018-10-26 19:04 ` Stefan Beller
2018-10-27 7:29 ` Junio C Hamano
2018-10-27 3:45 ` Taylor Blau
2018-10-27 6:27 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqftwsdevm.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).