From: Heiko Stuebner via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: Etienne Carriere <etienne.carriere@foss.st.com>,
Quentin Schulz <quentin.schulz@cherry.de>,
heiko@sntech.de, Heiko Stuebner <heiko.stuebner@cherry.de>
Subject: [Buildroot] [PATCH v2] package/arm-trusted-firmware: add ARM_TRUSTED_FIRMWARE_CPE_ID_*
Date: Thu, 26 Mar 2026 11:10:33 +0100 [thread overview]
Message-ID: <20260326101033.587997-1-heiko@sntech.de> (raw)
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.
Signed-off-by: Heiko Stuebner <heiko.stuebner@cherry.de>
---
changes in v2:
- remove lts- from lts releases
- remove "v" from version, to actually match version used in CPEs
boot/arm-trusted-firmware/arm-trusted-firmware.mk | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/boot/arm-trusted-firmware/arm-trusted-firmware.mk b/boot/arm-trusted-firmware/arm-trusted-firmware.mk
index b81ce0d827..c3c4a581da 100644
--- a/boot/arm-trusted-firmware/arm-trusted-firmware.mk
+++ b/boot/arm-trusted-firmware/arm-trusted-firmware.mk
@@ -5,6 +5,10 @@
################################################################################
ARM_TRUSTED_FIRMWARE_VERSION = $(call qstrip,$(BR2_TARGET_ARM_TRUSTED_FIRMWARE_VERSION))
+ARM_TRUSTED_FIRMWARE_CPE_ID_PREFIX = cpe:2.3:o
+ARM_TRUSTED_FIRMWARE_CPE_ID_VENDOR = arm
+ARM_TRUSTED_FIRMWARE_CPE_ID_PRODUCT = trusted_firmware-a
+ARM_TRUSTED_FIRMWARE_CPE_ID_VERSION = $(subst v,,$(subst lts-,,$(ARM_TRUSTED_FIRMWARE_VERSION)))
ifeq ($(BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_TARBALL),y)
# Handle custom ATF tarballs as specified by the configuration
--
2.51.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-03-26 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 10:10 Heiko Stuebner via buildroot [this message]
2026-03-26 11:37 ` [Buildroot] [PATCH v2] package/arm-trusted-firmware: add ARM_TRUSTED_FIRMWARE_CPE_ID_* Quentin Schulz 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=20260326101033.587997-1-heiko@sntech.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