test: Add tests for computeM1 and computeM2#23
Merged
Conversation
bodgit
force-pushed
the
add-tests-for-m1-m2
branch
from
7de7403 to
811ea1d
Compare
bodgit
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adds tests for
computeM1andcomputeM2.I introduced a new internal/rfc2945 subpackage because M1 and M2 are not part of the RFC 5054 appendix test vectors and are only described in RFC 2945.
I’ll extend the M1 test further in the follow-up PR for the RFC 5054 compatibility flag.