-
Notifications
You must be signed in to change notification settings - Fork 267
Normalize p256 #433
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
Closed
Closed
Normalize p256 #433
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
2426551
Implemented NormalizeLow for p256::Scalar
x87-va 205d40e
Merge branch 'master' of https://github.com/RustCrypto/elliptic-curve…
b5f2f3b
Fixed formatting
690c334
Updated p256/src/ecdsa.rs
x87-va 92f84d5
Merge branch 'master' of https://github.com/RustCrypto/elliptic-curve…
x87-va d22400f
Update p256/src/ecdsa.rs
x87-va b734264
Merge branch 'master' of https://github.com/RustCrypto/elliptic-curve…
x87-va File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's a bit excessive to loop in
num-bigintjust for testing this.k256does a number of other equivalence tests of the field arithmetic with it.I think ideally we'd even get rid of those and move all of that sort of testing into a
proptestscrate or something.For the purposes of testing this, I think it's fine to use
crypto_bigint::UIntto compute the various boundary conditions and then check if they're low/high.