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

[WIP ] v1.7 - Cryptography WG #615

Draft
wants to merge 1 commit into
base: 1.7-dev
Choose a base branch
from
Draft

[WIP ] v1.7 - Cryptography WG #615

wants to merge 1 commit into from

Conversation

n1ckl0sk0rtge
Copy link

2024-10-17

  • add serial number to certificateProperties
  • add fingerPrint to certificateProperties and relatedCryptoMaterialProperties

TODO/DONE

  • JSON schema modified
  • XML schema modified
  • ProtoBuf schema modified
  • JSON examples/test data crafted
  • XML examples/test data crafted
  • ProtoBuf examples/test data crafted

@n1ckl0sk0rtge
add certificate extensions, rename certificateExtensions to certifica…
1656690 
…teFileExtensions, fix relatedCryptographicAssets, add reason for certificate lifecycle

Signed-off-by: Nicklas Körtge <[email protected]>
jkowalleck
jkowalleck reviewed Mar 21, 2025
View reviewed changes
schema/bom-1.7.schema.json
"value": {
"type": "string",
"title": "Value",
"description": "The description of the custom certificate extension."
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"description": "The description of the custom certificate extension."
"description": "The value of the custom certificate extension."

#543 (comment)

@jkowalleck jkowalleck added this to the 1.7 milestone Mar 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jkowalleck jkowalleck jkowalleck left review comments

Assignees
No one assigned
Labels
proposed core enhancement
Projects
None yet
Milestone
1.7
Development

Successfully merging this pull request may close these issues.
2 participants
@n1ckl0sk0rtge @jkowalleck