Remove schemes that are no longer under consideration by NIST #238
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
|
Should we create an archive for the old schemes? Or is the git-history archive enough? Or mutiple folders such as |
This was referenced Sep 26, 2022
|
Finally got around to run the benchmarks with the most recent Arm toolchain ( |
|
@rpls, can we merge this? |
SIKE got broken by https://eprint.iacr.org/2022/975 The SIKE team acknowledged it in https://csrc.nist.gov/csrc/media/Projects/post-quantum-cryptography/documents/round-4/submissions/sike-team-note-insecure.pdf
|
I rebased on top of #244. |
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.
The goal of pqm4 was always to evaluate NIST PQC candidates and I believe we should keep it like that.
My plan is to keep the best implementations of winners and the round-4 candidates and add any suitable candidates submitted the signature on-ramp.
PQClean is probably going down the same path. I've opened a PR there, too: PQClean/PQClean#448.
I've created a tag for the current code: https://github.com/mupq/pqm4/releases/tag/Round3.
Are there any objections or opinions?
I've also benchmarked everything with the most recent Arm toolchain (arm-none-eabi-gcc (Arm GNU Toolchain 11.3.Rel1) 11.3.1 20220712 from https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads).