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: re-enable HKDF crypto functionality #34767
Conversation
['sha256', 'secret', 'salt', 'info', 10], | ||
['sha512', 'secret', 'salt', '', 15], | ||
]; | ||
-if (!common.hasOpenSSL3) |
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.
Can we expose a property common.openSSLisBoringSSL
based on the build time constant OPENSSL_IS_BORINGSSL
that is already available in upstream Node.js. It could simplify the patch in a upstream friendly way.
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.
@deepak1556 it's stalled but i actually started that ages ago: nodejs/node#38928
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.
Oh cool, btw agree with the concern in nodejs/node#38928 (review), shouldn't the change be
#ifdef OPENSSL_IS_BORINGSSL
#define IS_BORINGSSL 1
NODE_DEFINE_CONSTANT(target, IS_BORINGSSL);
#undef IS_BORINGSSL
#endif
Release Notes Persisted
|
* fix: re-enable HKDF crypto functionality * chore: update patches Co-authored-by: PatchUp <73610968+patchup[bot]@users.noreply.github.com>
* fix: re-enable HKDF crypto functionality * chore: update patches Co-authored-by: PatchUp <73610968+patchup[bot]@users.noreply.github.com>
Description of Change
Closes #31634.
Enables HKDF support in embedded Node.js as a result of https://boringssl-review.googlesource.com/c/boringssl/+/52829.
Checklist
npm test
passesRelease Notes
Notes: Enable missing HKDF support in Node.js
crypto
.