RFR: 8347938: Switch to latest ML-KEM private key encoding

Mark Powers mpowers at openjdk.org
Wed Apr 30 20:01:47 UTC 2025


On Wed, 30 Apr 2025 15:43:31 GMT, Weijun Wang <weijun at openjdk.org> wrote:

> The private key encoding formats of ML-KEM and ML-DSA are updated to match the latest IETF drafts at: https://datatracker.ietf.org/doc/html/draft-ietf-lamps-dilithium-certificates-08 and https://datatracker.ietf.org/doc/html/draft-ietf-lamps-kyber-certificates-10. New security/system properties are introduced to determine which CHOICE a private key is encoded.
> 
> Both the encoding and the expanded format are stored inside a `NamedPKCS8Key` now. When loading from a PKCS #8 key, the expanded format is either calculated or copied from the input.

test/jdk/sun/security/provider/named/NamedEdDSA.java line 1:

> 1: /*

I didn't expect an EdDSA test in this PQC bug fix.

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/24969#discussion_r2069359592


More information about the security-dev mailing list