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?
to your account
See section v2.3 of this paper: https://www.secg.org/sec1-v2.pdf
This is not urgent, but required before we release publicly, as we're dependent on Libsodium's internal state at the moment.
Related to #208
The text was updated successfully, but these errors were encountered:
I spent some time researching the need to use a different encoding (SEC1 v2) for the signature as generated by the libsodium library. From what I can see the checks in the verify code are to prevent the malleability of the signature.
Sorry, something went wrong.
In my opinion we should continue to use the libsodium 64 byte encoding of the Signature (R, s).
Agreed. According to what @hewison-chris found, the points are already stored in canonical form.
No branches or pull requests