-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
crypto: fix SHAKE128/256 breaking change introduced with OpenSSL 3.4 #58942
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
Review requested:
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #58942 +/- ##
==========================================
+ Coverage 90.07% 90.08% +0.01%
==========================================
Files 640 640
Lines 188473 188516 +43
Branches 36972 36986 +14
==========================================
+ Hits 169763 169830 +67
+ Misses 11427 11392 -35
- Partials 7283 7294 +11
🚀 New features to boost your workflow:
|
Reverts: nodejs#56160 Fixes: nodejs#56159 Fixes: nodejs#58913 Refs: nodejs#58121
This reverts commit e799722.
This reverts commit e6a988d.
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 work @panva!
// TODO: ideally we have to ship https://github.com/nodejs/node/pull/58121 so | ||
// that a proper DEP0198 deprecation can be done here as well. |
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.
// TODO: ideally we have to ship https://github.com/nodejs/node/pull/58121 so | |
// that a proper DEP0198 deprecation can be done here as well. | |
// TODO(panva): ideally we have to ship https://github.com/nodejs/node/pull/58121 | |
// so that a proper DEP0198 deprecation can be done here as well. |
Thank you for the reviews. I think I'll wait for #58121 to ship and then include its code in the deprecation. |
Landed in f5da8f8 |
Reverts: nodejs#56160 Fixes: nodejs#56159 Fixes: nodejs#58913 Refs: nodejs#58121 PR-URL: nodejs#58942 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: Joyee Cheung <[email protected]>
Reverts: nodejs#56160 Fixes: nodejs#56159 Fixes: nodejs#58913 Refs: nodejs#58121 PR-URL: nodejs#58942 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: Joyee Cheung <[email protected]>
Reverts: #56160 Fixes: #56159 Fixes: #58913 Refs: #58121 PR-URL: #58942 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: Joyee Cheung <[email protected]>
Background:
This PR:
crypto.createHash().update().digest()
until crypto: support outputLength option in crypto.hash for XOF functions #58121 gets on trackAfter this lands a semver-majorPRs that contain breaking changes and should be released in the next major version.
will follow with a runtime deprecation.
This will need backporting all the way back to 20.x
Reverts: #56160
Fixes: #56159
Fixes: #58913
Refs: #58121
Note: FWIW #56160 should not have landed. Any OpenSSL version-related test changes should only accomodate changes in codes, not behaviour.