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
fix: bad assertion in crypto functions that use BN_bn2bin_padded #17220
Conversation
in particular, this picks up electron/node#70a78f07b, which fixes an issue with incorrect usage of the BN_bn2bin_padded API in boringssl
This will need a manual backport to 4 and 5. |
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.
Nice catch, thanks!
one error seems to be:
🤔 and the other seems to be
|
@nornagon any reason this needs backport to 4.x ? AFAIK the changes on electron/node only made it to electron 5.x branch. |
ack, you're right, no need for 4. |
Release Notes Persisted
|
I have automatically backported this PR to "5-0-x", please check out #17255 |
…ctron#17220) * chore: roll node in particular, this picks up electron/node#70a78f07b, which fixes an issue with incorrect usage of the BN_bn2bin_padded API in boringssl * fix tests
in particular, this picks up electron/node#70a78f07b, which fixes an issue with incorrect usage of the BN_bn2bin_padded API in boringssl. This also adds tests to make sure those functions are fixed.
Checklist
npm test
passesRelease Notes
Notes: Fixed an assertion when calling
ECDH.getPrivateKey()
,diffieHellman.generateKeys()
ordiffieHellman.get*()
.