From: "Mikko Rapeli" <mikko.rapeli@bmw.de>
To: <zhengrq.fnst@fujitsu.com>
Cc: <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] db: correct CVE_PRODUCT
Date: Mon, 19 Apr 2021 06:59:26 +0000 [thread overview]
Message-ID: <YH0qTWrdEX5VH3eS@korppu> (raw)
In-Reply-To: <1618839901-127113-1-git-send-email-zhengrq.fnst@fujitsu.com>
On Mon, Apr 19, 2021 at 09:45:01PM +0800, zhengruoqin wrote:
> In the CVE database, now it use db2 instead of oracle_berkeley_db.
> So, in order to be handled correctly by CVE check, modify CVE_ PRODUCT.
Which CVEs, please add an example? In the past oracle_berkeley_db was used.
I wonder if both would need to be there, or if using the new value is
sufficient from now on.
-Mikko
> Signed-off-by: Zheng Ruoqin <zhengrq.fnst@fujitsu.com>
> ---
> meta/recipes-support/db/db_5.3.28.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-support/db/db_5.3.28.bb b/meta/recipes-support/db/db_5.3.28.bb
> index 9cb57e6a53..05720053f4 100644
> --- a/meta/recipes-support/db/db_5.3.28.bb
> +++ b/meta/recipes-support/db/db_5.3.28.bb
> @@ -15,7 +15,7 @@ HOMEPAGE = "https://www.oracle.com/database/technologies/related/berkeleydb.html
> LICENSE = "Sleepycat"
> RCONFLICTS_${PN} = "db3"
>
> -CVE_PRODUCT = "oracle_berkeley_db"
> +CVE_PRODUCT = "db2"
> CVE_VERSION = "11.2.${PV}"
>
> PR = "r1"
> --
> 2.25.1
>
>
>
>
next prev parent reply other threads:[~2021-04-19 6:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 13:45 [OE-core] [PATCH] db: correct CVE_PRODUCT zhengruoqin
2021-04-19 6:01 ` Chen Qi
2021-04-19 6:59 ` Mikko Rapeli [this message]
2021-04-20 1:55 ` zhengruoqin
2021-04-20 2:27 ` Chen Qi
[not found] ` <16776F7A4F5368B1.4443@lists.openembedded.org>
2021-04-20 2:40 ` Chen Qi
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=YH0qTWrdEX5VH3eS@korppu \
--to=mikko.rapeli@bmw.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=zhengrq.fnst@fujitsu.com \
/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