Skip to content

fix: use hashAlgorithm in PBES1 pattern - #1152

Open
aaronormerod wants to merge 1 commit into
CycloneDX:masterfrom
aaronormerod:fix/pbes1-variant-pattern
Open

aaronormerod wants to merge 1 commit into
CycloneDX:masterfrom
aaronormerod:fix/pbes1-variant-pattern

Conversation

@aaronormerod

Copy link
Copy Markdown
Contributor

As discussed in #906, the PBES1 variant pattern takes {hashAlgorithm} instead of {kdf}. RFC 8018 section 6.1 builds PBES1 on PBKDF1, which is parameterised by a hash algorithm.

Registry data only, no schema change. The family list is unchanged.

fixes #906

RFC 8018 section 6.1 builds PBES1 on PBKDF1, which takes a hash
algorithm, not a KDF.

Fixes CycloneDX#906

Signed-off-by: aaronormerod <137795541+aaronormerod@users.noreply.github.com>
@aaronormerod
aaronormerod requested a review from a team as a code owner October 12, 2026 10:16
@jkowalleck jkowalleck added the cap: cryptography-registry Capability: Cryptography Registry label Oct 12, 2026
@Mehrn0ush

Copy link
Copy Markdown
Contributor

LGTM

This branch has not been deployed

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

Labels

cap: cryptography-registry Capability: Cryptography Registry

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Defect]: Variant pattern for PBES1 must have {hashAlgorithm} instead of {kdf}

3 participants