From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: Heiko Thiery <heiko.thiery@gmail.com>
Cc: Thomas Perale <thomas.perale@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] utils/generate-cyclonedx: add uuid as serialNumber
Date: Fri, 18 Sep 2026 10:32:30 +0200 [thread overview]
Message-ID: <20260918083230.33707-1-thomas.perale@mind.be> (raw)
In-Reply-To: <20260918073631.665322-1-heiko.thiery@gmail.com>
Hi Heiko,
Thanks for the submission !
In reply of:
> In CycloneDX the serialNumber field is an optional top-level field that
> uniquely identified a SBOM using a URN RFC 4122 UUID format.
>
Initially I didn't include this field for reproducibility concerns: generating
an SBOM from the same configuration wouldn't generate the same output.
Of course this is exactly the goal of this field from the spec point of view
but I was concerned this could be an issue for Buildroot. So I didn't include
this field and thought it could be set by the end user if needed like other
fields such as:
- version
- metadata
- ...
One of the idea I thought about to solve this would be for user to be able to
define a template the `generate-cyclonedx` would take as basis for the
generation.
```json
{
"serialNumber": "{uuid.uuid4().urn}",
"metadata": {
"timestamp": "{datetime.now}"
"authors": {
"name": "..."
}
}
}
```
But i don't know if it feasible or nice to deal with from a user point of view.
Is there a tool you are using that enforce setting this field ?
Also in the commit message I would include the link to the spec:
https://cyclonedx.org/docs/1.6/json/#serialNumber
PERALE Thomas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-09-18 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 7:36 [Buildroot] [PATCH] utils/generate-cyclonedx: add uuid as serialNumber Heiko Thiery
2026-09-18 8:32 ` Thomas Perale via buildroot [this message]
2026-09-18 8:58 ` Heiko Thiery
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=20260918083230.33707-1-thomas.perale@mind.be \
--to=buildroot@buildroot.org \
--cc=heiko.thiery@gmail.com \
--cc=thomas.perale@mind.be \
/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