-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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: return result of openssl HMAC_Update instead of just true. #10891
Conversation
384ff19
to
8e22ab4
Compare
Updated commit (force push on my branch) just updates original commit message to reference the issue number. |
LGTM if CI is ok: https://ci.nodejs.org/job/node-test-pull-request/5941/ |
I must be missing something b/c when I review the output of test/arm I don't see a failure... |
@tmeisenh It's an issue with the github bot that sends the results back, if it's green on ci.nodejs.org (which it is), then CI passed. CI is green |
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.
LGTM but the commit log's status line should be <= 50 characters.
@gibfahn Awesome, thanks for the explanation. |
If you wouldn't mind amending the commit message, you'll save whoever lands this a few keystrokes. But if you don't update it, whoever lands it can update it for you, so either way, really. |
Fixes coverity scan issue 55489.
8e22ab4
to
2dc9920
Compare
Updated commit message |
HMAC_Update(&ctx_, reinterpret_cast<const unsigned char*>(data), len); | ||
return true; | ||
int r = HMAC_Update(&ctx_, reinterpret_cast<const unsigned char*>(data), len); | ||
return r == 1; |
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.
Looks like it can only occur with engines: openssl/openssl@87d52468aa600e023, so untestable.
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.
OK, debugged, it does look the digests return 1
on success, and always do this for software digests, so LGTM
Running CI again only because the pushing of the amended commit message theoretically may have accidentally included a code change or something. Just being thorough. |
Landed in 5ea98fb, thanks. |
Fixes coverity scan issue 55489. PR-URL: #10891 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Sam Roberts <[email protected]> Reviewed-By: Brian White <[email protected]>
Fixes coverity scan issue 55489. PR-URL: #10891 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Sam Roberts <[email protected]> Reviewed-By: Brian White <[email protected]>
Fixes coverity scan issue 55489. PR-URL: nodejs#10891 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Sam Roberts <[email protected]> Reviewed-By: Brian White <[email protected]>
Fixes coverity scan issue 55489. PR-URL: nodejs#10891 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Sam Roberts <[email protected]> Reviewed-By: Brian White <[email protected]>
Fixes coverity scan issue 55489. PR-URL: #10891 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Sam Roberts <[email protected]> Reviewed-By: Brian White <[email protected]>
Fixes coverity scan issue 55489. PR-URL: #10891 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Sam Roberts <[email protected]> Reviewed-By: Brian White <[email protected]>
Fixes coverity scan issue 55489. PR-URL: #10891 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Sam Roberts <[email protected]> Reviewed-By: Brian White <[email protected]>
Fixes coverity scan issue 55489. PR-URL: #10891 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Sam Roberts <[email protected]> Reviewed-By: Brian White <[email protected]>
Addresses coverity scan issue 55489
The existing tests pass but I did not add any new tests. I did not see any existing tests around error handling of openssl functions nor any test harness to allow you to do so.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)
crypto