Skip to content

Conversation

@n1ckl0sk0rtge
Copy link
Contributor

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

…teFileExtensions, fix relatedCryptographicAssets, add reason for certificate lifecycle

Signed-off-by: Nicklas Körtge <nicklas.koertge1@ibm.com>
"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)

stevespringett and others added 13 commits March 21, 2025 22:07
Signed-off-by: Steve Springett <steve@springett.us>
Signed-off-by: Basil Hess <bhe@zurich.ibm.com>
Extending the ikev2TransformTypes property
Signed-off-by: Basil Hess <bhe@zurich.ibm.com>
Ikev2 transform types extension (2)
- Adds a few more algorithm
- Converts urls to standards to doi links, where available.
- Checks if urls work

Signed-off-by: Basil Hess <bhe@zurich.ibm.com>
Signed-off-by: Basil Hess <bhe@zurich.ibm.com>
- Adds a few more algorithm
- Converts urls to standards to doi links, where available.
- Checks if urls work

----

TODO / progress
- [x] JSON schema
- [ ] XML schema
- [ ] ProtoBugf schema

<!-- 
Thank you for taking the time to develop and contribute a core
enhancement or fix for a defect!

We kindly request that you create pull requests only for things that
have been discussed in a ticket first; exceptions may be made for
spelling or grammar fixes.
Read more about the process here:
https://cyclonedx.org/participate/standardization-process/#working-model

Please have the related ticket/issue ID ready. 
If there is none, feel free to create a new ticket:
https://github.com/CycloneDX/specification/issues/new/choose

-->

<!-- 

Please provide a brief description of what this pull request intends to
do and which ticket it fixes/closes.
Example: 
> As discussed in ticket CycloneDX#485, this PR adds Streebog to the hash
algorithm enum.
>
> fixes CycloneDX#485 

In case this is for a spelling or grammar improvement, please provide a
brief description.
Example:
> Fixe typo: color(AE) -> colour(BE)

-->
IKE transform types: Only one algorithm per parameter
@jkowalleck jkowalleck self-requested a review April 18, 2025 08:00
bhess and others added 5 commits May 14, 2025 12:59
Signed-off-by: Basil Hess <bhe@zurich.ibm.com>
- Changes schma for crypto-defs to allow different variant patterns corresponding to different primitives
- Adds "key-wrap" as a new primitive

Signed-off-by: Basil Hess <bhe@zurich.ibm.com>
Signed-off-by: Basil Hess <bhe@zurich.ibm.com>
- Extends cryptography-defs.json list with algorithms from PKCS11
- Changes schma for crypto-defs to allow different variant patterns
corresponding to different primitives
- Adds "key-wrap" as a new primitive
@n1ckl0sk0rtge n1ckl0sk0rtge deleted the 1.7-dev-cryptography branch May 22, 2025 13:23
@JoeyLupo
Copy link

Were these proposed changes abandoned @n1ckl0sk0rtge? This looked like a major improvement from v1.6, especially in the certificate modeling.

@n1ckl0sk0rtge
Copy link
Contributor Author

Hi @JoeyLupo, I ran into some issues with this PR/branch during the rebase process, so I decided to close it and open a new one. All the previous changes, along with some additional updates, can now be found here.

@JoeyLupo
Copy link

Hmm, the new branch seems to not include the certificateExtensions field from https://github.com/n1ckl0sk0rtge/specification/blob/49abb613d21b8e6a2f8c69b444ba6523ca1362b1/schema/bom-1.7.schema.json#L5515:

                        "meta:enum": {
                          "basicConstraints": "Specifies whether a certificate can be used as a CA certificate or not.",
                          "keyUsage": "Specifies the allowed uses of the public key in the certificate.",
                          "extendedKeyUsage": "Specifies additional purposes for which the public key can be used.",
                          "subjectAlternativeName": "Allows inclusion of additional names to identify the entity associated with the certificate.",
                          "authorityKeyIdentifier": "Identifies the public key of the CA that issued the certificate.",
                          "subjectKeyIdentifier": "Identifies the public key associated with the entity the certificate was issued to.",
                          "authorityInformationAccess": "Contains CA issuers and OCSP information.",
                          "certificatePolicies": "Defines the policies under which the certificate was issued and can be used.",
                          "crlDistributionPoints": "Contains one or more URLs where a Certificate Revocation List (CRL) can be obtained.",
                          "signedCertificateTimestamp": "Shows that the certificate has been publicly logged, which helps prevent the issuance of rogue certificates by a CA. Log ID, timestamp and signature as proof.",
                        },

I think the inclusion of these fields is a major improvement over v1.6 and should certainly be included in v1.7.

@n1ckl0sk0rtge
Copy link
Contributor Author

@JoeyLupo, you are right! Thanks for pointing out! I will double check for other properties, and will add the certificateExtension.

@n1ckl0sk0rtge
Copy link
Contributor Author

@JoeyLupo: Here is the PR with all the changes, that were missing #658. Thanks again!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants