Git development
 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, 23 Sep 2026 14:47:18 -0700	[thread overview]
Message-ID: <xmqqwlsb63o9.fsf@gitster.g> (raw)
In-Reply-To: <arQ/nOH+o3XwQFD/@szeder.dev> ("SZEDER Gábor"'s message of "Wed, 23 Sep 2026 23:07:40 +0200")

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.

> ...
> I added that 'cat err' to see the error message.  Turns out that 'git
> ls-remote' can't even find the repository on the remote, but the
> prereq is still considered fulfilled.  Is that right?
> ...
> This time the error message talks about missing OCSP response, but the
> prereq is still considered fulfilled.  Again: is that right?!
>
> Instead of the lack of a certain string in the error message, is
> there something positive that we can test instead?

Oh, that is a very constructive and useful suggestion.  Greatly
appreciated.

> So this test case fails for me with the following trace output:
>
>   expecting success of 5585.5 'revoked certificate is accepted without http.sslVerifyStatus': 
>   	with_ssl_verification git ls-remote "$HTTPD_URL/smart/repo.git" >actual &&
>   	test_line_count -gt 0 actual
>   
>   + with_ssl_verification git ls-remote https://127.0.0.1:5585/smart/repo.git
>   + sane_unset GIT_SSL_NO_VERIFY
>   + unset GIT_SSL_NO_VERIFY
>   + return 0
>   + GIT_SSL_CAINFO=/home/szeder/src/git/t/trash directory.t5585-http-ssl-ocsp/httpd/ca.pem git ls-remote https://127.0.0.1:5585/smart/repo.git
>   fatal: unable to access 'https://127.0.0.1:5585/smart/repo.git/': server certificate verification failed. CAfile: /home/szeder/src/git/t/trash directory.t5585-http-ssl-ocsp/httpd/ca.pem CRLfile: none
>   error: last command exited with $?=128
>   not ok 5 - revoked certificate is accepted without http.sslVerifyStatus
>   #	
>   #		with_ssl_verification git ls-remote "$HTTPD_URL/smart/repo.git" >actual &&
>   #		test_line_count -gt 0 actual
>   #	
>  
> libcurl is 7.81.0, apache is 2.4.52 (whatever is shipped in this
> slowly aging LTS...)

Thanks.


  reply	other threads:[~2026-09-23 21:47 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 [this message]
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
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=xmqqwlsb63o9.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox