Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Ranjitsinh Rathod" <ranjitsinhrathod1991@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][dunfell][PATCH] c-ares: Fix forgotten PV bump to 1.16.1
Date: Mon, 17 Jan 2022 03:13:33 -0800	[thread overview]
Message-ID: <30882.1642418013855401778@lists.openembedded.org> (raw)
In-Reply-To: <0173f3da37397b1c9fb379b677310f379fba5fec.camel@lists.verisure.com>

[-- Attachment #1: Type: text/plain, Size: 437 bytes --]

Hi all,

I think during https://git.openembedded.org/meta-openembedded-contrib/commit/?h=stable/dunfell-nut&id=9ce3df8c2a10b45aa3695cf257aa27fd346d52a7 patch merge, PV variable is not updated and so CVE-2020-14354 is reported by cve tool. So removing PV can solve this.

I have verified using "bitbake -c cve_check c-ares" and after removing the PV variable, cve tool is not reporting CVE-2020-14354 anymore.

Thanks,
Ranjitsinh

[-- Attachment #2: Type: text/html, Size: 916 bytes --]

  reply	other threads:[~2022-01-17 11:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11 12:54 [meta-oe][dunfell][PATCH] c-ares: Bump PV to 1.16.1 Ernst Sjöstrand
2022-01-11 16:39 ` [oe] " Khem Raj
2022-01-12  7:06   ` [meta-oe][dunfell][PATCH] c-ares: Fix forgotten PV bump " Ernst Sjöstrand
2022-01-17 11:13     ` Ranjitsinh Rathod [this message]
2022-01-25  8:14     ` Ernst Sjöstrand

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=30882.1642418013855401778@lists.openembedded.org \
    --to=ranjitsinhrathod1991@gmail.com \
    --cc=openembedded-devel@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