Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Yoann Congal" <yoann.congal@smile.fr>
To: <deeratho@cisco.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][wrynose][PATCH 1/2] gnutls: Fix CVE-2026-3832
Date: Mon, 20 Jul 2026 13:19:54 +0200	[thread overview]
Message-ID: <DK3CWFWYP9UE.5WID74XZESIV@smile.fr> (raw)
In-Reply-To: <20260720110548.2458865-1-deeratho@cisco.com>

On Mon Jul 20, 2026 at 1:05 PM CEST, Deepak Rathore via lists.openembedded.org wrote:
> From: Deepak Rathore <deeratho@cisco.com>
>
> This patch applies the upstream fix [1] and test coverage [2], as
> referenced in [3], to address multi-record OCSP response handling where
> GnuTLS could check revocation status from the wrong OCSP entry.
>
> [1] https://gitlab.com/gnutls/gnutls/-/commit/731861b9de8dccaf7d3b0c1446833051e48670c2
> [2] https://gitlab.com/gnutls/gnutls/-/commit/d52d5f4f383e8c5d8e9a03334f2421ff35d37d2e
> [3] https://security-tracker.debian.org/tracker/CVE-2026-3832
>
> Reference:
> https://nvd.nist.gov/vuln/detail/CVE-2026-3832
>
> Signed-off-by: Deepak Rathore <deeratho@cisco.com>

Hello,

All that series should be tagged v2 with a changelog where appropriate:
https://docs.yoctoproject.org/dev/contributor-guide/submit-changes.html#taking-patch-review-into-account

Can you resend it with the v2 tag? You can use -v2 if you use git-send-email.

Adding these tags/changelog helps me a lot when tracking patch status.

Thanks!
-- 
Yoann Congal
Smile ECS



  parent reply	other threads:[~2026-07-20 11:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20 11:05 [OE-core][wrynose][PATCH 1/2] gnutls: Fix CVE-2026-3832 Deepak Rathore -X (deeratho - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-07-20 11:05 ` [OE-core][wrynose][PATCH 2/2] gnutls: Fix CVE-2026-42009 Deepak Rathore -X (deeratho - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-07-20 11:19 ` Yoann Congal [this message]
2026-07-20 11:42   ` [OE-core][wrynose][PATCH 1/2] gnutls: Fix CVE-2026-3832 Deepak Rathore -X (deeratho - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-07-20 11:40 ` [OE-core][wrynose][PATCH v2 " Deepak Rathore -X (deeratho - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-07-20 11:40   ` [OE-core][wrynose][PATCH v2 2/2] gnutls: Fix CVE-2026-42009 Deepak Rathore -X (deeratho - E INFOCHIPS PRIVATE LIMITED at Cisco)
  -- strict thread matches above, loose matches on Subject: below --
2026-07-10  9:53 [OE-core][wrynose][PATCH 1/2] gnutls: Fix CVE-2026-3832 Sudhir Dumbhare -X (sudumbha - E INFOCHIPS PRIVATE LIMITED at Cisco)

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=DK3CWFWYP9UE.5WID74XZESIV@smile.fr \
    --to=yoann.congal@smile.fr \
    --cc=deeratho@cisco.com \
    --cc=openembedded-core@lists.openembedded.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