-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8347938: Switch to latest ML-KEM private key encoding #23376
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
/issue add JDK-8347941 |
|
👋 Welcome back weijun! A progress list of the required criteria for merging this PR into |
|
❗ This change is not yet ready to be integrated. |
|
@wangweij |
|
@wangweij The following labels will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command. |
|
/label remove core-libs |
|
@wangweij |
|
@wangweij |
Webrevs
|
|
A new commit has been pushed. The most significant change is renaming
|
|
@wangweij This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
|
@wangweij This pull request has been inactive for more than 8 weeks and will now be automatically closed. If you would like to continue working on this pull request in the future, feel free to reopen it! This can be done using the |
The private key encoding formats of ML-KEM and ML-DSA are updated to match the latest IERTF drafts at: https://datatracker.ietf.org/doc/html/draft-ietf-lamps-dilithium-certificates-06 and https://datatracker.ietf.org/doc/html/draft-ietf-lamps-kyber-certificates-07. Most importantly, the seed used to generate a key pair is now stored in the private key.
Both the seed and the expanded format are stored inside a
NamedPKCS8Keynow. When loading from a PKCS #8 key that contains the seed, both fields will be filled. If the PKCS #8 encoding only contains the expanded key (which does not conform to the current drafts but might have been created earlier), the expanded key will be read and used in KEM and signature operations.Progress
Issues
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/23376/head:pull/23376$ git checkout pull/23376Update a local copy of the PR:
$ git checkout pull/23376$ git pull https://git.openjdk.org/jdk.git pull/23376/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 23376View PR using the GUI difftool:
$ git pr show -t 23376Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/23376.diff
Using Webrev
Link to Webrev Comment