Skip to content

fix: make FFDH ephemeral E optional - #1148

Open
Mehrn0ush wants to merge 1 commit into
CycloneDX:masterfrom
Mehrn0ush:fix/ffdh-optional-e
Open

Mehrn0ush wants to merge 1 commit into
CycloneDX:masterfrom
Mehrn0ush:fix/ffdh-optional-e

Conversation

@Mehrn0ush

@Mehrn0ush Mehrn0ush commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • Change FFDH(E)[-{namedGroup}] to FFDH[E][-{namedGroup}] so ephemeral E is optional, matching ECDH[E].
  • FFDH, FFDHE, and FFDHE-{namedGroup} are all valid constructed names.

Thanks @bhess

Closes #1147

Test plan

  • Diff is only the FFDH pattern
  • cryptography-defs.json still parses
  • FFDH and FFDHE-ffdhe2048 match the new pattern; FFDH(E) is gone

FFDH(E) grouped a required E, so only FFDHE names matched. Align with
ECDH[E] and RFC 7919: E is ephemeral and optional.

Signed-off-by: Mehrn0ush <mehrnoush.vaseghi@gmail.com>
@Mehrn0ush
Mehrn0ush requested a review from a team as a code owner October 9, 2026 08:43

@jvdsn jvdsn left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Seems like this was a typo. I always assumed it was optional.

@jkowalleck jkowalleck added the cap: cryptography-registry Capability: Cryptography Registry label Oct 14, 2026

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]: FFDH pattern treats ephemeral E as required

3 participants