All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: graysongordon-gl <graysongordon1@gmail.com>,
	 ps@pks.im, git@vger.kernel.org,  peff@peff.net,
	 avarab@gmail.com
Subject: Re: [PATCH v7] http: add http.sslVerifyStatus to check stapled OCSP responses
Date: Wed, 07 Oct 2026 11:18:40 -0700	[thread overview]
Message-ID: <xmqq33uh8jcv.fsf@gitster.g> (raw)
In-Reply-To: <arTUNYVvCNwX1pDp@szeder.dev> ("SZEDER Gábor"'s message of "Thu, 24 Sep 2026 09:41:41 +0200")

SZEDER Gábor <szeder.dev@gmail.com> writes:

> On Wed, Sep 23, 2026 at 02:47:18PM -0700, Junio C Hamano wrote:
>> SZEDER Gábor <szeder.dev@gmail.com> writes:
>> 
>> > On Tue, Sep 15, 2026 at 12:23:48PM -0400, graysongordon-gl wrote:
>> >> From: Grayson Gordon <graysongordon1@gmail.com>
>> >> 
>> >> git never sets CURLOPT_SSL_VERIFYSTATUS, so libcurl never requests the
>> >> OCSP "Certificate Status Request" extension and any stapled response a
>> >> server sends is ignored, including responses that explicitly state the
>> >> certificate has been revoked.
>> > ...
>> > This patch was merged to 'next' the other day, and the last test in
>> > the new t5585 fails on my system.
>> 
>> Sorry about a premature merge.  Since we are not in a hurry to take
>> this topic in (or no new feature topic in general), let me revert it
>> out of 'next' and give it a clean slate to try again.
>
> Well, if you hadn't merged it, we would perhaps still be none the
> wiser, because, alas, I don't have the bandwidth to run tests on the
> seen branch regularly...
>
> However, CI does, but I can't seem to find any CI runs that failed
> because of this, which makes me worried that something is wrong on my
> end.

Well, I was bisecting between jch..seen, making a wishful assumption
that there is only one topic to blame the recent CI timeouts (see
[*1*] and [*2*] for examples) that many linux-* jobs spin forever
and time out after 6 hours, for the past few days.  I finally found
out that 'seen' with this topic ejected, even though it seems to
fail jobs that depend on older version of Ubuntu, does not exhibit
the time-out-after-spinning-for-6-hours symptom ([*3*]).

So tentatively I am ejecting it out of 'seen'.  It might be some
funny interactions with other topics; I haven't tried to push it
alone to see what happens there at CI to test.


[References]

*1* https://github.com/git/git/actions/runs/37377476653
*2* https://github.com/git/git/actions/runs/37568540157
*3* https://github.com/git/git/actions/runs/37662034989


  parent reply	other threads:[~2026-10-07 18:18 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-11 17:02 [PATCH] http: add http.sslVerifyStatus to check stapled OCSP responses graysongordon-gl
2026-08-11 19:28 ` Junio C Hamano
2026-08-11 20:44 ` [PATCH v2] " graysongordon-gl
2026-08-12  6:25   ` Patrick Steinhardt
2026-08-12 15:53     ` Grayson Gordon
2026-08-12 14:17   ` Junio C Hamano
2026-08-12 18:25     ` [PATCH v3] " graysongordon-gl
2026-08-12 21:34       ` Junio C Hamano
2026-08-13 16:06         ` Junio C Hamano
2026-08-17 18:52           ` [PATCH v4] " graysongordon-gl
2026-08-17 19:19             ` Junio C Hamano
2026-08-18  7:50             ` Patrick Steinhardt
2026-08-18 14:51               ` Grayson Gordon
2026-08-19  8:14                 ` Patrick Steinhardt
2026-08-18 16:40               ` Junio C Hamano
2026-08-18 19:37           ` [PATCH v5] " graysongordon-gl
2026-08-18 20:12             ` Junio C Hamano
2026-08-18 21:22               ` Grayson Gordon
2026-08-18 21:48           ` [PATCH v6] " graysongordon-gl
2026-08-26 22:01             ` Junio C Hamano
2026-08-28 13:51               ` Grayson Gordon
2026-08-28 17:20                 ` Junio C Hamano
2026-08-31  6:56                   ` Patrick Steinhardt
2026-08-31 14:16                     ` Junio C Hamano
2026-08-31 14:24                       ` Patrick Steinhardt
2026-08-31 14:31                         ` Junio C Hamano
2026-09-08 12:55                           ` Grayson Gordon
2026-09-15 16:23                           ` [PATCH v7] " graysongordon-gl
2026-09-16 19:29                             ` Junio C Hamano
2026-09-23 12:42                             ` Patrick Steinhardt
2026-09-23 21:43                               ` Junio C Hamano
2026-09-23 21:07                             ` SZEDER Gábor
2026-09-23 21:47                               ` Junio C Hamano
2026-09-24  7:41                                 ` SZEDER Gábor
2026-09-24  7:59                                   ` Patrick Steinhardt
2026-09-25  9:28                                     ` SZEDER Gábor
2026-09-25 16:13                                       ` Junio C Hamano
2026-09-24 16:22                                   ` Junio C Hamano
2026-10-07 18:18                                   ` Junio C Hamano [this message]
2026-10-08  4:57                                     ` Junio C Hamano

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=xmqq33uh8jcv.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=graysongordon1@gmail.com \
    --cc=peff@peff.net \
    --cc=ps@pks.im \
    --cc=szeder.dev@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.