Skip to content

Conversation

PranavSenthilnathan
Copy link
Member

@PranavSenthilnathan PranavSenthilnathan commented Oct 10, 2025

Draft 12 of the Composite ML-DSA spec now requires the parameters to be present for ECPrivateKey. This PR implements these changes in our managed Composite ML-DSA implementation.

@PranavSenthilnathan PranavSenthilnathan marked this pull request as ready for review October 10, 2025 19:36
@Copilot Copilot AI review requested due to automatic review settings October 10, 2025 19:36
Copy link
Contributor

@Copilot 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 updates the Composite ML-DSA implementation to comply with Draft 12 of the specification, which now requires parameters to be present in ECPrivateKey structures. The key change is that ECPrivateKey objects must now include curve parameters (OID) for composite ML-DSA algorithms.

  • Updates ECPrivateKey generation to include required curve parameters
  • Modifies validation logic to enforce parameter presence and correctness
  • Updates size calculations to account for the additional parameter data

Reviewed Changes

Copilot reviewed 5 out of 6 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
CompositeMLDsaManaged.cs Updates draft specification references from version 08 to 12
CompositeMLDsaManaged.ECDsa.cs Adds parameter validation and generation for ECPrivateKey structures
CompositeMLDsaAlgorithm.cs Updates size calculations to include parameter overhead
CompositeMLDsaTestHelpers.cs Updates expected key size calculations with specific values per algorithm
CompositeMLDsaFactoryTests.cs Updates test cases to reflect new parameter requirements and validation

Copy link
Member

@jeffhandley jeffhandley left a comment

Choose a reason for hiding this comment

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

Let's wait for review from @bartonjs or @vcsjones to merge, but looks good to me. This would also have my support for backporting to 10.0 GA.

/cc @artl93

@PranavSenthilnathan PranavSenthilnathan added the breaking-change Issue or PR that represents a breaking API or functional change over a prerelease. label Oct 14, 2025
@PranavSenthilnathan
Copy link
Member Author

No APIs changed but, following our past convention, implementing an updated PQC draft requires a breaking change doc. Assuming we get this in for .NET 10, we can just modify dotnet/docs#48901.

@dotnet-policy-service dotnet-policy-service bot added the needs-breaking-change-doc-created Breaking changes need an issue opened with https://github.com/dotnet/docs/issues/new?template=dotnet label Oct 14, 2025
Copy link
Contributor

Added needs-breaking-change-doc-created label because this PR has the breaking-change label.

When you commit this breaking change:

  1. Create and link to this PR and the issue a matching issue in the dotnet/docs repo using the breaking change documentation template, then remove this needs-breaking-change-doc-created label.
  2. Ask a committer to mail the .NET Breaking Change Notification DL.

Tagging @dotnet/compat for awareness of the breaking change.

@PranavSenthilnathan PranavSenthilnathan enabled auto-merge (squash) October 20, 2025 20:03
@PranavSenthilnathan
Copy link
Member Author

/ba-g #103347

@PranavSenthilnathan PranavSenthilnathan merged commit 9f15c72 into dotnet:main Oct 20, 2025
85 of 87 checks passed
@PranavSenthilnathan PranavSenthilnathan deleted the cmldsa-draft11 branch October 20, 2025 23:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-System.Security breaking-change Issue or PR that represents a breaking API or functional change over a prerelease. needs-breaking-change-doc-created Breaking changes need an issue opened with https://github.com/dotnet/docs/issues/new?template=dotnet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants