We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It's my understanding that this library uses SUPERCOP which uses Ref10 which omitted a check for S<l to prevent malleability.
Is this corrected in the nacl library?
http://stackoverflow.com/a/19162037/1382306 http://crypto.stackexchange.com/questions/14712/non-standard-signature-security-definition-conforming-ed25519-malleability/
The text was updated successfully, but these errors were encountered:
The check was added in 4099618 I am not convinced that this is necessary, but I hardly see any practical downsides either.
This breaks compatibility with other implementations, though. So if none of them follow, this might be reverted before the next release is tagged.
Sorry, something went wrong.
No branches or pull requests
It's my understanding that this library uses SUPERCOP which uses Ref10 which omitted a check for S<l to prevent malleability.
Is this corrected in the nacl library?
http://stackoverflow.com/a/19162037/1382306
http://crypto.stackexchange.com/questions/14712/non-standard-signature-security-definition-conforming-ed25519-malleability/
The text was updated successfully, but these errors were encountered: