-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Migrate EC support to Rust #9024
Conversation
1e6f9e6
to
751388c
Compare
80e407e
to
2b1ef37
Compare
Note to self: Do we have a test that verifies that we always serialize in named curve form? |
let valid = verifier.verify(data, signature).unwrap_or(false); | ||
// TODO: Empty the error stack. BoringSSL leaves one in the event of | ||
// signature validation failure. Upstream to rust-openssl? | ||
openssl::error::ErrorStack::get(); |
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.
Should we annotate this for just boring?
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.
Done, but also, what do you think about upstreaming?
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 we should upstream. Without doing so every caller needs to know that they need this conditional or else their error stack gets polluted and who knows what their error handling does.
No description provided.