From: Quentin Schulz via buildroot <buildroot@buildroot.org>
To: Heiko Stuebner <heiko@sntech.de>, buildroot@buildroot.org
Cc: Etienne Carriere <etienne.carriere@foss.st.com>,
Heiko Stuebner <heiko.stuebner@cherry.de>
Subject: Re: [Buildroot] [PATCH] package/arm-trusted-firmware: add ARM_TRUSTED_FIRMWARE_CPE_ID_*
Date: Wed, 25 Mar 2026 19:12:33 +0100 [thread overview]
Message-ID: <d728395d-316b-4ab6-be7e-bba218dcf31a@cherry.de> (raw)
In-Reply-To: <20260325150346.414826-1-heiko@sntech.de>
Hi Heiko,
On 3/25/26 4:03 PM, Heiko Stuebner wrote:
> From: Heiko Stuebner <heiko.stuebner@cherry.de>
>
> Trusted-Firmware has been using a number of CPE identifiers in the past
> but especially after v2.4, the correct identifier would be similar
> to cpe:2.3:o:arm:trusted_firmware-a:2.12:rc0:*:*:-:*:*:*
>
> https://nvd.nist.gov/products/cpe/detail/65DEC230-1CD5-40DB-903A-22537D1E44FE
>
> Add the relevant CPE fields to the trusted-firmware package.
>
Thinking about it a bit more, I **think** we may want to strip lts-
prefix for the CPE_ID_VERSION. I don't see any version past 2.4 on NVD
so we cannot really know what they'll do once they need to tackle LTSes,
but I am assuming they are NOT going to use the lts- prefix?
What do you think?
Cheers,
Quentin
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-03-25 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 15:03 [Buildroot] [PATCH] package/arm-trusted-firmware: add ARM_TRUSTED_FIRMWARE_CPE_ID_* Heiko Stuebner via buildroot
2026-03-25 16:11 ` Quentin Schulz via buildroot
2026-03-25 18:12 ` Quentin Schulz via buildroot [this message]
2026-03-26 10:14 ` Heiko Stuebner via buildroot
-- strict thread matches above, loose matches on Subject: below --
2024-02-28 14:51 Christian Hitz via buildroot
2024-03-03 17:07 ` Arnout Vandecappelle 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=d728395d-316b-4ab6-be7e-bba218dcf31a@cherry.de \
--to=buildroot@buildroot.org \
--cc=etienne.carriere@foss.st.com \
--cc=heiko.stuebner@cherry.de \
--cc=heiko@sntech.de \
--cc=quentin.schulz@cherry.de \
/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