public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Changqing Li <changqing.li@windriver.com>
To: "Mittal, Anuj" <anuj.mittal@intel.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [V2][PATCH] rpm: fix CVE-2021-3521
Date: Fri, 31 Dec 2021 10:18:41 +0800	[thread overview]
Message-ID: <e1cda44a-9c13-07b0-a643-9ec41ff9a1c9@windriver.com> (raw)
In-Reply-To: <e6d34fc6a7dd35b26b1d9396081f417ac439fa24.camel@intel.com>


On 12/31/21 9:51 AM, Mittal, Anuj wrote:
> [Please note: This e-mail is from an EXTERNAL e-mail address]
>
> On Thu, 2021-12-23 at 14:12 +0800, Changqing Li wrote:
>> From: Changqing Li <changqing.li@windriver.com>
>>
>> Signed-off-by: Changqing Li <changqing.li@windriver.com>
>> ---
>>   .../rpm/files/0001-CVE-2021-3521.patch        |  57 +++
>>   .../rpm/files/0002-CVE-2021-3521.patch        |  64 ++++
>>   .../rpm/files/0003-CVE-2021-3521.patch        | 329
>> ++++++++++++++++++
>>   meta/recipes-devtools/rpm/rpm_4.17.0.bb       |   3 +
>>   4 files changed, 453 insertions(+)
>>   create mode 100644 meta/recipes-devtools/rpm/files/0001-CVE-2021-
>> 3521.patch
>>   create mode 100644 meta/recipes-devtools/rpm/files/0002-CVE-2021-
>> 3521.patch
>>   create mode 100644 meta/recipes-devtools/rpm/files/0003-CVE-2021-
>> 3521.patch
>>
>> diff --git a/meta/recipes-devtools/rpm/files/0001-CVE-2021-3521.patch
>> b/meta/recipes-devtools/rpm/files/0001-CVE-2021-3521.patch
>> new file mode 100644
>> index 0000000000..b374583017
>> --- /dev/null
>> +++ b/meta/recipes-devtools/rpm/files/0001-CVE-2021-3521.patch
>> @@ -0,0 +1,57 @@
>> +From 9a6871126f472feea057d5f803505ec8cc78f083 Mon Sep 17 00:00:00
>> 2001
>> +From: Panu Matilainen <pmatilai@redhat.com>
>> +Date: Thu, 30 Sep 2021 09:56:20 +0300
>> +Subject: [PATCH 1/3] Refactor pgpDigParams construction to helper
>> function
>> +
>> +No functional changes, just to reduce code duplication and needed by
>> +the following commits.
>> +
>> +CVE: CVE-2021-3521
>> +Upstream-Staus:
> Should be Upstream-Status. This is triggering build failures for
> master-next.

Sorry,  I will fix this and send a V3

> Thanks,
>
> Anuj


      reply	other threads:[~2021-12-31  2:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-23  6:12 [V2][PATCH] rpm: fix CVE-2021-3521 changqing.li
2021-12-31  1:51 ` [OE-core] " Mittal, Anuj
2021-12-31  2:18   ` Changqing Li [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=e1cda44a-9c13-07b0-a643-9ec41ff9a1c9@windriver.com \
    --to=changqing.li@windriver.com \
    --cc=anuj.mittal@intel.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