Skip to content
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

src: remove redundant AESCipherMode #54438

Merged

Conversation

tniessen
Copy link
Member

For each supported variant of AES, we already have OpenSSL's associated NID, so we can simply retrieve the block cipher mode of operation from the NID.

For each supported variant of AES, we already have OpenSSL's associated
NID, so we can simply retrieve the block cipher mode of operation from
the NID.
@tniessen tniessen added crypto Issues and PRs related to the crypto subsystem. c++ Issues and PRs that require attention from people who are familiar with C++. labels Aug 18, 2024
@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/crypto

@nodejs-github-bot nodejs-github-bot added the needs-ci PRs that need a full CI run. label Aug 18, 2024
Copy link

codecov bot commented Aug 18, 2024

Codecov Report

Attention: Patch coverage is 62.50000% with 3 lines in your changes missing coverage. Please review.

Project coverage is 87.33%. Comparing base (e4f61de) to head (976ad25).
Report is 61 commits behind head on main.

Files Patch % Lines
src/crypto/crypto_aes.cc 62.50% 2 Missing and 1 partial ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##             main   #54438   +/-   ##
=======================================
  Coverage   87.33%   87.33%           
=======================================
  Files         648      648           
  Lines      182321   182322    +1     
  Branches    34971    34977    +6     
=======================================
+ Hits       159222   159229    +7     
+ Misses      16374    16371    -3     
+ Partials     6725     6722    -3     
Files Coverage Δ
src/crypto/crypto_aes.h 33.33% <ø> (ø)
src/crypto/crypto_aes.cc 52.33% <62.50%> (+0.15%) ⬆️

... and 20 files with indirect coverage changes

@tniessen tniessen added the request-ci Add this label to start a Jenkins CI on a PR. label Aug 18, 2024
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Aug 18, 2024
@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot

This comment was marked as outdated.

@tniessen tniessen added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Aug 19, 2024
@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot

This comment was marked as outdated.

@tniessen
Copy link
Member Author

None of the test failures seem related. But it's hard to believe that our CI is in such a bad state.

@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot
Copy link
Collaborator

@tniessen
Copy link
Member Author

The 10th CI run failed with this error:

13:04:49 Warning: Permanently added '67.158.54.159' (ED25519) to the list of known hosts.
13:04:49 remote: fatal: no such ref: jenkins-node-test-commit-windows-fanned-976ad25cdc982f96d20ef1e9267112db67e8ab39        
13:04:49 remote: git upload-archive: archiver died with error
13:04:50 fatal: sent error to the client: git upload-archive: archiver died with error
13:04:50 + git archive --format=tar --remote=binary_tmp@67.158.54.159:binary_tmp.git jenkins-node-test-commit-windows-fanned-976ad25cdc982f96d20ef1e9267112db67e8ab39 src/node_version.h -o node_version.h.tar
13:04:50 Warning: Permanently added '67.158.54.159' (ED25519) to the list of known hosts.
13:04:50 remote: fatal: no such ref: jenkins-node-test-commit-windows-fanned-976ad25cdc982f96d20ef1e9267112db67e8ab39        
13:04:50 remote: git upload-archive: archiver died with error
13:04:50 fatal: sent error to the client: git upload-archive: archiver died with error

@nodejs-github-bot
Copy link
Collaborator

@tniessen tniessen added the commit-queue Add this label to land a pull request using GitHub Actions. label Aug 27, 2024
@nodejs-github-bot nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Aug 27, 2024
@nodejs-github-bot nodejs-github-bot merged commit 74ea78d into nodejs:main Aug 27, 2024
68 checks passed
@nodejs-github-bot
Copy link
Collaborator

Landed in 74ea78d

RafaelGSS pushed a commit that referenced this pull request Aug 30, 2024
For each supported variant of AES, we already have OpenSSL's associated
NID, so we can simply retrieve the block cipher mode of operation from
the NID.

PR-URL: #54438
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
RafaelGSS pushed a commit that referenced this pull request Aug 30, 2024
For each supported variant of AES, we already have OpenSSL's associated
NID, so we can simply retrieve the block cipher mode of operation from
the NID.

PR-URL: #54438
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
@RafaelGSS RafaelGSS mentioned this pull request Aug 30, 2024
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants