-
Notifications
You must be signed in to change notification settings - Fork 522
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
P256 signatures don't verify? #851
Comments
Can you clarify what error you get? Are you sure that private and public keys really match? |
My apologies. I was testing this in the REPL and was misinterpreting the results. So, I'll turn this issue into a doc request: say that |
Returning a boolean as the signature verification result was actually the old behavior and it led to security issues because it is not always clear what the right value should be (is |
The first part makes a bit of sense, but the verb "verify" is pretty clear what the result would mean. The second part is antithetical to the purpose of documentation. Please consider adding "The result is undefined; verification failure is only represented by an exception." |
Greetings. I'm doing some simple signing and verifying with P256 keys and am failing even in trivial cases.
In fact, an even more trivial case fails:
Given the lack of exception text for .verify, I can't tell if there is something simple I'm missing, or if the verification just doesn't work. Any clues would be appreciated, and I'll feed anything I get back into the documentation.
The text was updated successfully, but these errors were encountered: