From: "Siddharth" <sdoshi@mvista.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [kirkstone][PATCH] openssl: Security fix for CVE-2024-4741
Date: Sun, 02 Jun 2024 10:52:23 -0700 [thread overview]
Message-ID: <918.1717350743959512876@lists.openembedded.org> (raw)
In-Reply-To: <AS1PR10MB5697AB1D0FEA8F5683503339FDFE2@AS1PR10MB5697.EURPRD10.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 529 bytes --]
>> Nitpick : above commit link references commit for CVE-2024-4603 (copy+paste error).
- Ahh, that's silly of me. Guess the cup of coffee didnt take away the drowsiness completely.. Thank-you for pointing it out.
>> The main problem of this patch (and the same patch for scarthgap) is that it's picking only one out of 5 commits referencing this CVE.
- That definately makes sense. I just followed the fix links from https://openssl.org/news/vulnerabilities.html and didnt dive deeper.
- I will send a v2 by tomorrow.
[-- Attachment #2: Type: text/html, Size: 2059 bytes --]
prev parent reply other threads:[~2024-06-02 17:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-02 16:45 [OE-core][kirkstone][PATCH] openssl: Security fix for CVE-2024-4741 Siddharth
2024-06-02 17:33 ` Marko, Peter
2024-06-02 17:52 ` Siddharth [this message]
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=918.1717350743959512876@lists.openembedded.org \
--to=sdoshi@mvista.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