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

Open Beginner friendly
#906 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Domain
cryptography

Research direction

Start by locating the Cryptography Registry entry for PBES1 and compare its variant pattern with the RFC8018 section cited in the issue. Replace {kdf} with {hashAlgorithm} where appropriate, then verify that the registry data changes without altering schema behavior or adding algorithms.

Written by the indexing model from the issue text.

Description

cap: cryptography-registry defect

Describe the defect

As per RFC8018 PBES1 combines the PBKDF1 function with an underlying block cipher. PBES1 is compatible with the encryption scheme in PKCS5_15. Therefore, the variable {hashAlgorithm} which is one of the parameters for the underlying PBKDF1 must be an element of the variant pattern instead of {kdf}.

Refer https://docs.oracle.com/en/java/javase/25/docs/specs/security/standard-names.html#cipher-algorithms for example of PBES1 usage.

Additional context

The issue is data-quality / naming defect in the Cryptography Registry and can be fixed without changing schema behavior or introducing new algorithms.

Dominant language
XSLT
Stars
551
Forks
93
Avg merge
4h 51m
Merged PRs (30d)
42

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CycloneDX/specification

All issues in CycloneDX/specification

Similar issues

More Cryptography issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.