utils/generate-cyclonedx: add uuid as serialNumber
PATCH 1/1 utils/generate-cyclonedx: add uuid as serialNumber
In CycloneDX the serialNumber field is an optional top-level field that uniquely identified a SBOM using a URN RFC 4122 UUID format.
--- utils/generate-cyclonedx | 2 ++ 1 file changed, 2 insertions(+)
utils/generate-cyclonedx +2 -0
@@ -19,6 +19,7 @@ import urllib.request import subprocess import sys import re +import uuid CYCLONEDX_VERSION = "1.6"
@@ -534,6 +535,7 @@ def main(): "bomFormat": "CycloneDX", "$schema": f"http://cyclonedx.org/schema/bom-{CYCLONEDX_VERSION}.schema.json", "specVersion": f"{CYCLONEDX_VERSION}", + "serialNumber": uuid.uuid4().urn, "metadata": { "component": { "bom-ref": args.project_name,
Signature · 6 lines
2.47.3 _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
Hi Heiko,
Thanks for the submission !
In reply of:
Quoted 3 lines
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
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
Hi Thomas,
Am Fr., 18. Sept. 2026 um 10:32 Uhr schrieb Thomas Perale <[email protected]>:
Quoted 10 lines
Hi Heiko,
Thanks for the submission !
In reply of:
Quoted 3 lines
In CycloneDX the serialNumber field is an optional top-level field that uniquely identified a SBOM using a URN RFC 4122 UUID format.
Quoted 7 lines
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:
Yes you are right, the spec says: "Every BOM generated SHOULD have a unique serial number, even if the contents of the BOM have not changed over time"
So I understand your concerns.
Quoted 9 lines
- 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-cyclonedxwould take as basis for the generation.
Quoted 11 lines
```json
{
"serialNumber": "{uuid.uuid4().urn}",
"metadata": {
"timestamp": "{datetime.now}"
"authors": {
"name": "..."
}
}
}
```Currently I use a post step to add the serialNumber field:
```
jq --arg sn "urn:uuid:$(cat /proc/sys/kernel/random/uuid)"
'{bomFormat, "$schema": .["$schema"], specVersion, serialNumber: $sn}
+ .' sbom.json
```Having a template sounds also a good idea. With that you would be free in adding all info in addition without modifying the script.
Quoted 5 lines
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 ?
There is no tool, but our company's security office requested this field for their process.
Quoted 4 lines
Also in the commit message I would include the link to the spec:
I can submit a v2 that adds this information.
Quoted 1 line
PERALE Thomas
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
Thomas, Heiko,
Quoted 8 lines · Heiko Thiery
Quoted 3 lines
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 ?
There is no tool, but our company's security office requested this field for their process.
Quoted 1 line
Quoted 5 lines
Quoted 3 lines
Also in the commit message I would include the link to the spec:
I can submit a v2 that adds this information.
So where do we stand with this?
If the CycloneDX spec requires this UUID, I would suggest that we include it, and people who want to compared CycloneDX files in terms of reproducibility will have to ignore this field.
Thomas
Signature · 7 lines
Thomas Petazzoni, co-owner and CEO, Bootlin Embedded Linux and Kernel engineering and training https://bootlin.com _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
Thomas, Heiko,
In reply of:
Quoted 18 lines
Thomas, Heiko,
Quoted 8 lines · Heiko Thiery
Quoted 3 lines
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 ?
There is no tool, but our company's security office requested this field for their process.
Quoted 1 line
Quoted 5 lines
Quoted 3 lines
Also in the commit message I would include the link to the spec:
I can submit a v2 that adds this information.
Quoted 7 lines
So where do we stand with this?
If the CycloneDX spec requires this UUID, I would suggest that we include it, and people who want to compared CycloneDX files in terms of reproducibility will have to ignore this field.
Thomas
It's optional in the CycloneDX spec but it _might_ be required by some regulations to have an unique identifier.
It's OK for me to include this change but I would still like to offer in the future a solution that can fit both uses cases: reproducibility and output customization with product owner informations/requirements.
Best regard,
PERALE Thomas
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
Quoted 2 lines · Thomas Perale
It's optional in the CycloneDX spec but it _might_ be required by some regulations to have an unique identifier.
Ah. Then maybe we should leave it out, and ask Heiko to post-process the CycloneDX SBOM produced by Buildroot to meet his cybersecurity folks requirements. And we can revisit that later if other people show up and ask for the same uuid field.
Quoted 3 lines
It's OK for me to include this change but I would still like to offer in the future a solution that can fit both uses cases: reproducibility and output customization with product owner informations/requirements.
Like "generate-cyclonedx --reproducible" ?
Thomas
Signature · 7 lines
Thomas Petazzoni, co-owner and CEO, Bootlin Embedded Linux and Kernel engineering and training https://bootlin.com _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
Thomas, Heiko,
In reply of:
Quoted 10 lines · Thomas Perale
Quoted 3 lines
It's optional in the CycloneDX spec but it _might_ be required by some regulations to have an unique identifier.
Ah. Then maybe we should leave it out, and ask Heiko to post-process the CycloneDX SBOM produced by Buildroot to meet his cybersecurity folks requirements. And we can revisit that later if other people show up and ask for the same uuid field.
Quoted 5 lines
Quoted 3 lines
It's OK for me to include this change but I would still like to offer in the future a solution that can fit both uses cases: reproducibility and output customization with product owner informations/requirements.
Like "generate-cyclonedx --reproducible" ?
Personal opinion but I would prefer to not add too many arguments to the script to keep it easy to use and readable.
My idea to is to be able to pass a JSON template that contains custom information and allows to use a set of tags that will insert information at runtime.
Here for example what the base template would look like for the reproducible SBOM:
```json
{
"bomFormat": "CycloneDX",
"$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json",
"specVersion": "1.6",
"metadata": {
"component": {
"type": "firmware",
"bom-ref": "buildroot",
"name": "buildroot",
"version": "@BR_VERSION@",
"cpe": "cpe:2.3:a:buildroot:buildroot:@BR_VERSION@:*:*:*:*:*:*:*"
},
"tools": {
"components": [
{
"type": "application",
"name": "Buildroot generate-cyclonedx",
"version": "@BR_VERSION@",
"licenses": [
{
"license": {
"id": "GPL-2.0"
}
}
]
}
]
}
}
}
```Here another example of a template someone developping a product with buildroot could use:
```json
{
"bomFormat": "CycloneDX",
"$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json",
"specVersion": "1.6",
"serialNumber": "@UUID@"
"metadata": {
"timestamp": "@TIMESTAMP@",
"lifecycles": [{
"phase": "post-build"
}],
"author": {
"name": "..."
},
"component": {
"type": "firmware"
"bom-ref": "my-product",
"name": "my-product",
"version": "@VCS_VERSION@",
"components": [
{
"type": "firmware"
"bom-ref": "buildroot",
"name": "buildroot",
"version": "@BR_VERSION@",
"cpe": "cpe:2.3:a:buildroot:buildroot:@BR_VERSION@:*:*:*:*:*:*:*"
}
]
},
"tools": {
"components": [
{
"type": "application",
"name": "Buildroot generate-cyclonedx",
"version": "@BR_VERSION@",
"licenses": [
{
"license": {
"id": "GPL-2.0"
}
}
]
}
]
}
}
}
```I don't have anything ready to present. But I think it address the needs of multiple user that want to add custom informations to the produced SBOM. For example:
- https://lore.kernel.org/all/[email protected]/
- https://lore.kernel.org/all/[email protected]/
Something similar is used by 'brotli' to generate their SBOM:
- https://github.com/google/brotli/blob/master/sbom.cdx.json
Personally, I think what Heiko is doing right now with 'jq' is unfortunately the correct way until we have a better solution implemented. If this series is applied I will have to use 'jq' to remove this property for my use cases so the problem is just moved to someone else ;)
Let me know what you think.
Best regards,
PERALE Thomas
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot