Skip to content

Conversation

@Lachstec
Copy link

This PR addresses Issue #916 by allowing users to directly sign the generated BOM by using the new flag --signing-key <filepath> and providing an RSA private key. Signature was tested with to verify without errors with the CycloneDX-CLI to ensure compatability.

  • Add new Flag --signing-key (short: -sk) to allow passing a private key
  • XmlBomSinger.cs handles signing the BOM using System.Security.Cryptography.Xml
  • Returns an Error if JSON Signing is used.

It would make sense to also allow signing JSON BOMs and allow the usage of X509 certificates. The CycloneDX-CLI does not seem to support that at this moment, so this PR only implements parity with it. Further work on this could be done in a follow up PR.

@Lachstec Lachstec requested a review from a team as a code owner October 14, 2025 17:14
Signed-off-by: Leon <leon@1ux.dev>
Signed-off-by: Leon <leon@1ux.dev>
Signed-off-by: Leon <leon@1ux.dev>
Signed-off-by: Leon <leon@1ux.dev>
Signed-off-by: Leon <leon@1ux.dev>
Signed-off-by: Leon <leon@1ux.dev>
@Lachstec Lachstec force-pushed the feature/sign-xml-bom branch from 83dc2cb to ed8253d Compare October 14, 2025 17:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant