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: Tue, 30 Oct 2018 11:09:59 +0900 [thread overview]
Message-ID: <xmqqftwo2nig.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1810291418300.4546@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Mon, 29 Oct 2018 14:22:16 +0100 (STD)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>> >> 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.
>> ...
>> Yeah, but "http.sslBackend can be used to choose betnween OpenSSL
>> and Scure Channel" applies only to Windows ...
> ...
>> > 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.
How's this?
On platforms with recent cURL library, http.sslBackend configuration
variable can be used to choose different SSL backend at runtime.
The Windows port uses this mechanism to switch between OpenSSL and
Secure Channel while talking over the HTTPS protocol.
next prev parent reply other threads:[~2018-10-30 2:10 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
2018-10-29 13:22 ` Johannes Schindelin
2018-10-30 2:09 ` Junio C Hamano [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqftwo2nig.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.
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 NNTP newsgroup(s).