-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
crypto: add separate error for INVALID_KEY_TYPE #37555
Closed
RaisinTen
wants to merge
3
commits into
nodejs:master
from
RaisinTen:crypto/add-separate-error-for-INVALID_KEY_TYPE
Closed
crypto: add separate error for INVALID_KEY_TYPE #37555
RaisinTen
wants to merge
3
commits into
nodejs:master
from
RaisinTen:crypto/add-separate-error-for-INVALID_KEY_TYPE
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nodejs-github-bot
added
c++
Issues and PRs that require attention from people who are familiar with C++.
crypto
Issues and PRs related to the crypto subsystem.
needs-ci
PRs that need a full CI run.
labels
Mar 1, 2021
cc @jasnell |
addaleax
approved these changes
Mar 1, 2021
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.
Maybe we could also expand CryptoErrorVector
in the future to forward error codes, rather than just plain strings, so that the errors become more programatically accessible?
RaisinTen
added
the
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
label
Mar 2, 2021
jasnell
approved these changes
Mar 5, 2021
Landed in 03942ca |
jasnell
pushed a commit
that referenced
this pull request
Mar 5, 2021
PR-URL: #37555 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: James M Snell <[email protected]>
danielleadams
pushed a commit
that referenced
this pull request
Mar 16, 2021
PR-URL: #37555 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: James M Snell <[email protected]>
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
c++
Issues and PRs that require attention from people who are familiar with C++.
crypto
Issues and PRs related to the crypto subsystem.
needs-ci
PRs that need a full CI run.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This addresses these TODO comments:
node/src/crypto/crypto_cipher.h
Lines 228 to 231 in e6cbec5
node/src/crypto/crypto_keys.h
Lines 348 to 351 in e6cbec5