Skip to content

Set encoding to expandedKey for ML-DSA and ML-KEM - #1718

Merged
jasonkatonica merged 1 commit into
IBM:java17from
jasonkatonica:katonica/issue/setexpandedpqc-java17
Aug 19, 2026
Merged

Set encoding to expandedKey for ML-DSA and ML-KEM#1718
jasonkatonica merged 1 commit into
IBM:java17from
jasonkatonica:katonica/issue/setexpandedpqc-java17

Conversation

@jasonkatonica

Copy link
Copy Markdown
Member

Add JVM system properties -Djdk.mldsa.pkcs8.encoding=expandedKey and -Djdk.mlkem.pkcs8.encoding=expandedKey to the Surefire argLine in both Surefire plugin configurations in pom.xml. This ensures ML-DSA and ML-KEM private keys use expanded encodings only.

Back-ported from: #1616

Signed-off-by: Jason Katonica katonica@us.ibm.com

Add JVM system properties -Djdk.mldsa.pkcs8.encoding=expandedKey and
-Djdk.mlkem.pkcs8.encoding=expandedKey to the Surefire argLine in
both Surefire plugin configurations in pom.xml. This ensures ML-DSA
and ML-KEM private keys use expanded encodings only.

Back-ported from: IBM#1616

Signed-off-by: Jason Katonica <katonica@us.ibm.com>
@jasonkatonica
jasonkatonica merged commit a65c5ad into IBM:java17 Aug 19, 2026
3 checks passed
@jasonkatonica
jasonkatonica deleted the katonica/issue/setexpandedpqc-java17 branch August 19, 2026 18:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants