Re: js/mingw-http-ssl, was Re: What's cooking in git.git (Oct 2018, #05; Fri, 26)
Hi Junio, On Tue, 30 Oct 2018, Junio C Hamano wrote: > Eric Sunshine writes: > > > On Mon, Oct 29, 2018 at 10:10 PM Junio C Hamano wrote: > >> How's this? > >> > >> On platforms with recent cURL library, http.sslBackend configuration > >> variable can be used to choose different SSL backend at runtime. > > > > s/choose/& a/ > > > >> The Windows port uses this mechanism to switch between OpenSSL and > >> Secure Channel while talking over the HTTPS protocol. > > Thanks. > > By the way, I am beginning to like this phrasing quite a lot. It > encourages those with other ports like Linux and Mac to see if they > want a similar runtime switching by singling out Windows port, which > was what I wanted to achive with the original one, but I think the > updated text does so more effectively. I like it, too! Thanks, Dscho
Re: js/mingw-http-ssl, was Re: What's cooking in git.git (Oct 2018, #05; Fri, 26)
Hi Junio, On 30 October 2018 11:07:39 GMT+05:30, Junio C Hamano wrote: >Eric Sunshine writes: >>> On platforms with recent cURL library, http.sslBackend >configuration >>> variable can be used to choose different SSL backend at runtime. >> >> s/choose/& a/ >> >>> The Windows port uses this mechanism to switch between OpenSSL >and >>> Secure Channel while talking over the HTTPS protocol. > >Thanks. > >By the way, I am beginning to like this phrasing quite a lot. It >encourages those with other ports like Linux and Mac to see if they >want a similar runtime switching by singling out Windows port, which >was what I wanted to achive with the original one, but I think the >updated text does so more effectively. The new phrasing seems to be reading quite better indeed. -- Sivaraam Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: js/mingw-http-ssl, was Re: What's cooking in git.git (Oct 2018, #05; Fri, 26)
Eric Sunshine writes: > On Mon, Oct 29, 2018 at 10:10 PM Junio C Hamano wrote: >> How's this? >> >> On platforms with recent cURL library, http.sslBackend configuration >> variable can be used to choose different SSL backend at runtime. > > s/choose/& a/ > >> The Windows port uses this mechanism to switch between OpenSSL and >> Secure Channel while talking over the HTTPS protocol. Thanks. By the way, I am beginning to like this phrasing quite a lot. It encourages those with other ports like Linux and Mac to see if they want a similar runtime switching by singling out Windows port, which was what I wanted to achive with the original one, but I think the updated text does so more effectively.
Re: js/mingw-http-ssl, was Re: What's cooking in git.git (Oct 2018, #05; Fri, 26)
On Mon, Oct 29, 2018 at 10:10 PM Junio C Hamano wrote: > How's this? > > On platforms with recent cURL library, http.sslBackend configuration > variable can be used to choose different SSL backend at runtime. s/choose/& a/ > The Windows port uses this mechanism to switch between OpenSSL and > Secure Channel while talking over the HTTPS protocol.
Re: js/mingw-http-ssl, was Re: What's cooking in git.git (Oct 2018, #05; Fri, 26)
Johannes Schindelin 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.
Re: js/mingw-http-ssl, was Re: What's cooking in git.git (Oct 2018, #05; Fri, 26)
Hi Junio, On Fri, 26 Oct 2018, Junio C Hamano wrote: > Johannes Schindelin writes: > > > 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. On Linux, with an appropriately built libcurl, you can use http.sslBackend to choose between OpenSSL, GNU TLS, NSS and mbedTLS. > > 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. In contrast, I think that the main purpose of this patch series is to bring http.sslBackend to everybody. And then we also include fall-out patches that are Windows-only. :-) Ciao, Dscho
Re: js/mingw-http-ssl, was Re: What's cooking in git.git (Oct 2018, #05; Fri, 26)
Johannes Schindelin 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.
