From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Perale via buildroot <buildroot@buildroot.org>
Cc: Thomas Perale <thomas.perale@mind.be>
Subject: Re: [Buildroot] [PATCH] package/aardvark-dns: add CPE identifier
Date: Mon, 28 Jul 2025 22:47:33 +0200 [thread overview]
Message-ID: <20250728224733.1d1727e9@windsurf> (raw)
In-Reply-To: <20250727192537.1164560-1-thomas.perale@mind.be>
Hello,
On Sun, 27 Jul 2025 21:25:37 +0200
Thomas Perale via buildroot <buildroot@buildroot.org> wrote:
> The cpe:2.3:a:containers:aardvark-dns:*:*:*:*:*:*:*:* is
> valid for this package.
>
> See https://nvd.nist.gov/products/cpe/detail/5F79D5CD-D716-4190-BE08-31EB5EEB233F
>
> The CPE version strip the 'v' prefix from the version.
>
> Signed-off-by: Thomas Perale <thomas.perale@mind.be>
Reviewed-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
even though, I would really prefer us to be able to have the _VERSION
field without the v prefix in the first place. Indeed your tricky with
AARDVARK_DNS_CPE_ID_VERSION works for the CVE matching, but it doesn't
work for release-monitoring.org matching.
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
next prev parent reply other threads:[~2025-07-28 20:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-27 19:25 [Buildroot] [PATCH] package/aardvark-dns: add CPE identifier Thomas Perale via buildroot
2025-07-28 20:47 ` Thomas Petazzoni via buildroot [this message]
2025-07-29 20:02 ` Thomas Perale via buildroot
2025-07-30 8:27 ` Thomas Petazzoni via buildroot
2026-02-03 15:22 ` Julien Olivain via buildroot
2026-02-13 19:36 ` Thomas Perale via buildroot
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=20250728224733.1d1727e9@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.perale@mind.be \
--cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.