From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Gregory CLEMENT <gregory.clement@bootlin.com>
Cc: Matt Weber <matthew.weber@rockwellcollins.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v5 3/3] package/pkg-utils/cve.py: Manage case when package version doesn't exist
Date: Sun, 9 Jan 2022 17:34:27 +0100 [thread overview]
Message-ID: <20220109173427.07372dae@windsurf> (raw)
In-Reply-To: <20200921101515.132359-4-gregory.clement@bootlin.com>
On Mon, 21 Sep 2020 12:15:15 +0200
Gregory CLEMENT <gregory.clement@bootlin.com> wrote:
> Until now, when a package didn't report a version, then the CVE
> comparison was just skipped. It leads most of the time to declare the
> package not affected by the CVE.
>
> Instead of it, report the CVE_UNKNOWN status in order to be aware that
> the CVE related to this package has to be checked.
>
> Signed-off-by: Gregory CLEMENT <gregory.clement@bootlin.com>
Do you remember which packages/cases this was handling?
> if not pkg_version:
> + unknown_pkg_version = True
I've added a print() here, and did a full run of pkg-stats on all
packages, and did not get any match.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-01-09 16:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 10:15 [Buildroot] [PATCH v5 0/3] Improving CVE reporting Gregory CLEMENT
2020-09-21 10:15 ` [Buildroot] [PATCH v5 1/3] support/script/pkg-stats: Manage the CVEs that need to be check Gregory CLEMENT
2022-01-09 16:33 ` Thomas Petazzoni
2020-09-21 10:15 ` [Buildroot] [PATCH v5 2/3] support/script/cve-checker: " Gregory CLEMENT
2022-01-09 16:33 ` Thomas Petazzoni
2020-09-21 10:15 ` [Buildroot] [PATCH v5 3/3] package/pkg-utils/cve.py: Manage case when package version doesn't exist Gregory CLEMENT
2022-01-09 16:34 ` Thomas Petazzoni [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=20220109173427.07372dae@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=gregory.clement@bootlin.com \
--cc=matthew.weber@rockwellcollins.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