PQC Extension specification for FIPS 203, 204 and 205 #223
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
athoelke
added
enhancement
athoelke
requested review from
gilles-peskine-arm,
ndevillard and
MarcusJGStreets
This was referenced Oct 22, 2024
Draft
|
I've added a draft PDF rendering of the extension - see the top posting in this PR. |
|
I've marked this PR as 'ready for review':
|
athoelke
changed the title
* This presumes that Encapsulation and ECIES APIs have been added to the main specification
athoelke
force-pushed
the
crypto-ext-pqc
branch
from
d4f117e
to
e75fbb4
Compare
|
Rebased to remove an accidentally added file during the rework to create an extension. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR replaces #216, #218, and #220 by placing ML-KEM, ML-DSA, and SLH-DSA into a separate PQC Extension specification.
The X.509 interchange formats for the keys in these algorithms is still being determined within the IETF LAMPS working group. I propose that the default export formats for these key types should be aligned with the final RFC specifications from IETF.
This PR would enable the proposed Crypto API additions for these algorithms to be published in a Beta extension specification before the RFCs are finalized.
The content is almost entirely taken from the above PRs.
Updated draft PDF for the PQC Extension: AES0119-PSA_Certified_Crypto_API-1.3_PQC_Extension-bet.0-draft.1.pdf
First draft PDF for the PQC Extension:
AES0119-PSA_Certified_Crypto_API-1.3_PQC_Extension-bet.0-draft.pdfFixes #95
Fixes #96
Fixes #97