From: "Pawan Badganchi" <badganchipv@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [meta][kirkstone][PATCH 2/2] curl: Add fix for CVE-2023-23916
Date: Wed, 15 Mar 2023 02:59:43 -0700 [thread overview]
Message-ID: <19361.1678874383740050194@lists.openembedded.org> (raw)
In-Reply-To: <CAOSpxdZoxui1TuXFUpZ6N_Kt_nRBYYm9GvK4DLJ6J4g_B1rDVA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 434 bytes --]
Hello steve,
We have not taken patch from actual upstream because we have curl version 7.82 and in the actual upstream curl version is 7.88. So in our source code one variable is absent. Hence i had taken from launchpad. Now i have taken backport patch curl(7.81) from ubuntu trusted upstream.
https://lists.openembedded.org/g/openembedded-core/message/178529
https://lists.openembedded.org/g/openembedded-core/message/178530
[-- Attachment #2: Type: text/html, Size: 1264 bytes --]
next prev parent reply other threads:[~2023-03-15 9:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 7:50 [meta][kirkstone][PATCH 1/2] curl: Add fix for CVE-2023-23914, CVE-2023-23915 pawan
2023-03-03 7:50 ` [meta][kirkstone][PATCH 2/2] curl: Add fix for CVE-2023-23916 pawan
2023-03-14 15:39 ` [OE-core] " Steve Sakoman
2023-03-15 9:59 ` Pawan Badganchi [this message]
2023-03-14 15:37 ` [OE-core] [meta][kirkstone][PATCH 1/2] curl: Add fix for CVE-2023-23914, CVE-2023-23915 Steve Sakoman
2023-03-15 3:06 ` [kirkstone][PATCH v2] " mingli.yu
2023-03-15 16:14 ` Steve Sakoman
2023-03-22 5:45 ` [kirkstone][PATCH v3] " mingli.yu
-- strict thread matches above, loose matches on Subject: below --
2023-03-15 9:35 [meta][kirkstone][PATCH 1/2] " pawan
2023-03-15 9:35 ` [meta][kirkstone][PATCH 2/2] curl: Add fix for CVE-2023-23916 pawan
2023-03-20 13:07 ` Pawan Badganchi
2023-03-24 7:56 [meta][kirkstone][PATCH 1/2] curl: Add fix for CVE-2023-23914, CVE-2023-23915 pawan
2023-03-24 7:57 ` [meta][kirkstone][PATCH 2/2] curl: Add fix for CVE-2023-23916 pawan
2023-03-24 15:45 [OE-core] " Pawan Badganchi
2023-03-29 7:38 ` Pawan Badganchi
2023-03-29 14:18 [OE-core] " Steve Sakoman
2023-04-03 10:34 ` Pawan Badganchi
2023-04-03 10:41 ` Pawan Badganchi
2023-04-03 15:17 [OE-core] " Steve Sakoman
2023-04-03 15:22 ` Pawan Badganchi
2023-04-03 15:27 [OE-core] " Steve Sakoman
2023-04-03 15:44 ` Pawan Badganchi
2023-04-03 16:20 [OE-core] " Steve Sakoman
2023-04-03 17:00 ` Pawan Badganchi
2023-04-03 23:01 [OE-core] " Martin Jansa
2023-04-04 8:33 ` Pawan Badganchi
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=19361.1678874383740050194@lists.openembedded.org \
--to=badganchipv@gmail.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