Johannes Schindelin writes:
>> I did not and I do not think it would. I was wondering if the
>> ability to be able to specify these per destination is something
>> very useful and deserves to be called out in the doc, together with
>> ...
>
> I do not think that it needs to be called out
Hi Junio,
On Thu, 18 Oct 2018, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> >> In any case, you can use "http..$variable" to say "I want the
> >> http.$variable to be in effect but only when I am talking to ".
> >> Does it make sense for this new variable, too? That is, does it
>
Hi Junio,
On Thu, 25 Oct 2018, Junio C Hamano wrote:
> Eric Sunshine writes:
>
> > On Mon, Oct 15, 2018 at 6:14 AM Brendan Forster via GitGitGadget
> > wrote:
> >> This config value is only used if http.sslBackend is set to "schannel",
> >> which forces cURL to use the Windows Certificate
Eric Sunshine writes:
> On Mon, Oct 15, 2018 at 6:14 AM Brendan Forster via GitGitGadget
> wrote:
>> This config value is only used if http.sslBackend is set to "schannel",
>> which forces cURL to use the Windows Certificate Store when validating
>> server certificates associated with a remote
Johannes Schindelin writes:
>> In any case, you can use "http..$variable" to say "I want the
>> http.$variable to be in effect but only when I am talking to ".
>> Does it make sense for this new variable, too? That is, does it
>> benefit the users to be able to do something like this?
>>
>>
On Tue, Oct 16, 2018 at 02:25:57PM +0200, Johannes Schindelin wrote:
> > > That ">=" is hard to grok. I think you meant it to be pronounced
> > > "requries at least", but that is not a common reading. People more
> > > commonly pronounce it "is greater than or equal to".
> >
> > This seemed
Hi Peff,
On Tue, 16 Oct 2018, Jeff King wrote:
> On Tue, Oct 16, 2018 at 01:23:25PM +0900, Junio C Hamano wrote:
>
> > > +#if LIBCURL_VERSION_NUM >= 0x072c00
> > > + curl_easy_setopt(result, CURLOPT_SSL_OPTIONS,
> > > CURLSSLOPT_NO_REVOKE);
> > > +#else
> > > +
Hi Junio,
On Tue, 16 Oct 2018, Junio C Hamano wrote:
> "Brendan Forster via GitGitGadget" writes:
>
> > Note: an earlier iteration tried to use the config setting
> > http.schannel.checkRevoke, but the http.* config settings can be limited
> > to specific URLs via http..* (which would mistake
Hi Eric,
On Mon, 15 Oct 2018, Eric Sunshine wrote:
> On Mon, Oct 15, 2018 at 6:14 AM Brendan Forster via GitGitGadget
> wrote:
> > This config value is only used if http.sslBackend is set to "schannel",
> > which forces cURL to use the Windows Certificate Store when validating
> > server
On Tue, Oct 16, 2018 at 01:23:25PM +0900, Junio C Hamano wrote:
> > +#if LIBCURL_VERSION_NUM >= 0x072c00
> > + curl_easy_setopt(result, CURLOPT_SSL_OPTIONS,
> > CURLSSLOPT_NO_REVOKE);
> > +#else
> > + warning("CURLSSLOPT_NO_REVOKE not applied to curl SSL options
> >
"Brendan Forster via GitGitGadget" writes:
> Note: an earlier iteration tried to use the config setting
> http.schannel.checkRevoke, but the http.* config settings can be limited
> to specific URLs via http..* (which would mistake `schannel` for a
> URL).
Yeah, "http.schannel.anything" would
On Mon, Oct 15, 2018 at 6:14 AM Brendan Forster via GitGitGadget
wrote:
> This config value is only used if http.sslBackend is set to "schannel",
> which forces cURL to use the Windows Certificate Store when validating
> server certificates associated with a remote server.
>
> This is only
From: Brendan Forster
This adds support for a new http.schannelCheckRevoke config value.
This config value is only used if http.sslBackend is set to "schannel",
which forces cURL to use the Windows Certificate Store when validating
server certificates associated with a remote server.
This
13 matches
Mail list logo
