OQS encoding as per IETF116 #44
Merged
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
|
@ounsworth FYI/testing |
|
@baentsch You have changed: to this change should also be reflected in oid_mapping.md ... I'll do that right now. |
|
Looks good. Thanks for putting this together Michael and Mike! We had a big discussion on NCCoE about this pull request as well. |
johngray-dev
approved these changes
May 3, 2023
ounsworth
approved these changes
May 3, 2023
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.
Do not merge until tested!
This PR deposits artefacts using the IETF115 OIDs (except new Falcon OIDs in latest commit) and "classic" OQS key encoding format (as used at IETF115) but using the latest (IETF116) oqs-provider (incl. most current Falcon implementation).
Data re-generation can be done, e.g., by running within the "providers/oqs" directory