-
-
Couldn't load subscription status.
- Fork 33.6k
Revert "crypto: add crypto.timingSafeEqual" #8225
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
This reverts commit 0fc5e0d. Additional testing indicates that there may still be timing issues with this implementation. Revert in order to give more time for testing before this goes out into a release... Refs: nodejs#8040 Refs: nodejs#8203
|
LGTM @nodejs/crypto |
|
LGTM. This looks like it was a clean revert, no nudging necessary? |
|
Given the rather large impact this has on our CI results, I'd be OK with this landing sooner rather than waiting the usual 48 hours as long as it's a clean revert and there's no concerns from @nodejs/crypto. |
|
+1 for sooner rather than later. |
|
It is a clean revert. There were no conflicts. |
This reverts commit 0fc5e0d. Additional testing indicates that there may still be timing issues with this implementation. Revert in order to give more time for testing before this goes out into a release... Refs: #8040 Refs: #8203 PR-URL: #8225 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
|
Landed in 0764bc4 |
Checklist
make -j4 test(UNIX), orvcbuild test nosign(Windows) passesAffected core subsystem(s)
crypto
Description of change
This reverts commit 0fc5e0d.
Additional testing indicates that there may still be timing issues with this implementation. Revert in order to give more time for testing before this goes out into a release...
Refs: #8040
Refs: #8203
/cc @Trott @not-an-aardvark