Skip to content

Conversation

@Mehrn0ush
Copy link
Contributor

As discussed in ticket #767, this PR adds AES-CMAC-PRF-128 (RFC 4615) to the Cryptography Registry.

Fixes #767

Details

  • Adds AES-CMAC-PRF-128 as a mac variant under the existing AES family.
  • Adds authoritative standards reference for RFC 4615.
  • Registry-only change (schema/cryptography-defs.json). No schema or specification behavior changes.

@Mehrn0ush Mehrn0ush requested a review from a team as a code owner January 7, 2026 16:06
@stevespringett
Copy link
Member

@bhess

@stevespringett stevespringett added cap: cryptography Capability: Cryptography (CBOM) cap: cryptography-registry Capability: Cryptography Registry labels Jan 8, 2026
Copy link
Contributor

@bhess bhess left a comment

Choose a reason for hiding this comment

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

LGTM.

One change request: remove the "HPKE" avoid merge conflicts with #766

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR adds support for two new cryptographic algorithms to the registry: HPKE (Hybrid Public Key Encryption, RFC 9180) and AES-CMAC-PRF-128 (RFC 4615). However, the PR title and description only mention AES-CMAC-PRF-128, omitting the HPKE addition.

Changes:

  • Added HPKE algorithm family with RFC 9180 standard reference
  • Added AES-CMAC-PRF-128 variant under the existing AES family with RFC 4615 standard reference
Comments suppressed due to low confidence (2)

schema/cryptography-defs.json:11

  • Trailing whitespace after the closing brace and comma. This is inconsistent with the formatting used elsewhere in the file where closing braces have no trailing spaces.
        },

schema/cryptography-defs.json:11

  • Trailing whitespace after the closing brace and comma. This is inconsistent with the formatting used elsewhere in the file where closing braces have no trailing spaces.
        },

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

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

Labels

cap: cryptography Capability: Cryptography (CBOM) cap: cryptography-registry Capability: Cryptography Registry

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[FEATURE]: Add AES-CMAC-PRF-128 (RFC 4615) to Cryptography Registry

3 participants