-
Notifications
You must be signed in to change notification settings - Fork 16.9k
fix: ECDH.setPrivateKey correctly sets the key #27688
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
Conversation
ckerr
left a comment
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.
Would it make sense to add a regression test for this?
|
@ckerr this undisables the node test which would have caught this. |
|
@nornagon mind rebasing? |
|
Release Notes Persisted
|
|
I was unable to backport this PR to "12-x-y" cleanly; |
shnybans
left a comment
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.
Co-authored-by: Shelley Vohr <[email protected]>
Description of Change
Fixes #27687.
Checklist
npm testpassesRelease Notes
Notes: Fixed ECDH.setPrivateKey() not updating the key.