-
Notifications
You must be signed in to change notification settings - Fork 199
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
p384: v0.11 release tracking issue #566
Comments
@daviddrysdale would you be interested in helping add Wycheproof test vectors? |
@jedisct1 did you want to take a look at adding 32-bit support? If not, I probably can in the next few days |
#573 implemented (currently untested) 32-bit support except for field and scalar inversions, which presently use a 64-bit only implementation. Once that has been addressed, we can add |
Happy to put in something analogous to the P256 test vectors, but it doesn't seem like the various traits (e.g. |
@daviddrysdale I think I got it taken care of in #574 |
@tarcieri Is there anything left blocking the |
I was curious to try this transformation on the field arithmetic and what impact it would have on performance: RustCrypto/utils#768 I wouldn't consider it a release blocker, but it would be nice to have at least compile-time transformations to/from Montgomery form, if only so field element constants could be given in canonical form. It would also potentially enable computing basepoint tables at compile time. |
#589 adds After that it would be nice to expose And after that, I'm good to ship it! |
Released in #593 |
This is a tracking ticket for work items it would be nice to have before cutting a final v0.11 release which includes an initial arithmetic implementation.
NOTE: not all of these need to be completed prior to a release and they can be added after-the-fact.
cc @brycx @jedisct1
The text was updated successfully, but these errors were encountered: