Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Jacob Kroon" <jacob.kroon@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] rpm: Exclude CVE-2021-20266 from cve-check
Date: Mon, 17 May 2021 11:50:49 +0200	[thread overview]
Message-ID: <eab4eb99-b189-e8a9-d16d-d90cb748a331@gmail.com> (raw)
In-Reply-To: <20210517094834.2415783-1-richard.purdie@linuxfoundation.org>



On 5/17/21 11:48 AM, Richard Purdie wrote:
> This is included in the release we have, it was the reason for the last rpm
> point release.
> 
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---
>   meta/recipes-devtools/rpm/rpm_4.16.1.3.bb | 4 ++++
>   1 file changed, 4 insertions(+)
> 
> diff --git a/meta/recipes-devtools/rpm/rpm_4.16.1.3.bb b/meta/recipes-devtools/rpm/rpm_4.16.1.3.bb
> index 2857cd730c4..760adab02b5 100644
> --- a/meta/recipes-devtools/rpm/rpm_4.16.1.3.bb
> +++ b/meta/recipes-devtools/rpm/rpm_4.16.1.3.bb
> @@ -51,6 +51,10 @@ S = "${WORKDIR}/git"
>   # included in 4.16.1.3
>   CVE_CHECK_WHIETLIST += "CVE-2021-20271"
>   
> +# Fix https://github.com/rpm-software-management/rpm/commit/2e21a178fcc76565c09ed3a28624ca8aeda1880a
> +# included in 4.16.1.3
> +CVE_CHECK_WHIETLIST += "CVE-2021-20266"
> +

Is the same spelling already exists above, but is that really 
intentional, "WHIET" instead of "WHITE" ?

/Jacob

>   DEPENDS = "libgcrypt db file popt xz bzip2 elfutils python3"
>   DEPENDS_append_class-native = " file-replacement-native bzip2-replacement-native"
>   
> 
> 
> 
> 
> 

  reply	other threads:[~2021-05-17  9:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17  9:48 [PATCH] rpm: Exclude CVE-2021-20266 from cve-check Richard Purdie
2021-05-17  9:50 ` Jacob Kroon [this message]
2021-05-17  9:56   ` [OE-core] " Richard Purdie
     [not found]   ` <167FD211EC31BA98.24037@lists.openembedded.org>
2021-05-17 10:04     ` Richard Purdie

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=eab4eb99-b189-e8a9-d16d-d90cb748a331@gmail.com \
    --to=jacob.kroon@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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