Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Where to store a key size? #37

Closed
GeroDittmann opened this issue Oct 12, 2023 · 1 comment
Closed

Where to store a key size? #37

GeroDittmann opened this issue Oct 12, 2023 · 1 comment

Comments

@GeroDittmann
Copy link

We discussed two options to express a key size in algorithmProperties:

  1. Use an existing security strength field. (Was this referring to the classicalSecurityLevel field?)
  2. Introduce a new field, keysize or just size (to alternatively cover block size etc. where required) or something along those lines.

IIUC the security strength concept might be intuitive enough for the community—probably helped by some documentation how to set and interpret it.
@bhess bhess mentioned this issue Nov 16, 2023
Merged
stevespringett added a commit to CycloneDX/specification that referenced this issue Nov 16, 2023
@stevespringett
CBOM: adds 'parameterSetIdentifier' property, replacing 'variant' (#339)
779121c 
The new property 'parameterSetIdentifier' replaces 'variant' and
contains information about the parameter set identifying an algorithm.
This can be, for example, the key length (in AES), the digest length (in
SHA2), or the hash algorithm used internally (in SLH-DSA / FIPS205). The
"description" field contains some examples.

This PR is motivated by IBM/CBOM#37 and
intends to address its use case.

Tagging @stevespringett, @n1ckl0sk0rtge, @mrutkows, @GeroDittmann
@bhess
Copy link
Member

bhess commented Apr 9, 2024

Closing with the upstream to CycloneDX 1.6 and the merge of CycloneDX/specification#339.

@bhess bhess closed this as completed Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bhess @GeroDittmann