Skip to content

Conversation

@sam-github
Copy link
Contributor

@thealphanerd can you point me to another PR like this, so I can structure it the right way (explain its a backport, etc).

Checklist
  • make -j8 test (UNIX), or vcbuild test nosign (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines
Affected core subsystem(s)
Description of change

Fix a regression introduced in commit 2996b5c ("crypto: Allow GCM
ciphers to have a longer IV length") from April 2016 where a misplaced
parenthesis in a 'is ECB cipher?' check made it possible to use empty
IVs with non-ECB ciphers.

Also fix some exit bugs in test/parallel/test-crypto-authenticated.js
that were introduced in commit 4a40832 ("test: cleanup IIFE tests")
where removing the IFFEs made the test exit prematurely instead of just
skipping subtests.

PR-URL: #9032
Refs: #6376
Refs: #9024
Reviewed-By: Anna Henningsen [email protected]
Reviewed-By: Fedor Indutny [email protected]
Reviewed-By: Shigeki Ohtsu [email protected]

Fix a regression introduced in commit 2996b5c ("crypto: Allow GCM
ciphers to have a longer IV length") from April 2016 where a misplaced
parenthesis in a 'is ECB cipher?' check made it possible to use empty
IVs with non-ECB ciphers.

Also fix some exit bugs in test/parallel/test-crypto-authenticated.js
that were introduced in commit 4a40832 ("test: cleanup IIFE tests")
where removing the IFFEs made the test exit prematurely instead of just
skipping subtests.

PR-URL: nodejs#9032
Refs: nodejs#6376
Refs: nodejs#9024
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Fedor Indutny <[email protected]>
Reviewed-By: Shigeki Ohtsu <[email protected]>
@nodejs-github-bot nodejs-github-bot added c++ Issues and PRs that require attention from people who are familiar with C++. v4.x labels Nov 18, 2016
@mscdex
Copy link
Contributor

mscdex commented Nov 18, 2016

Backports should target the appropriate -staging branch.

@sam-github
Copy link
Contributor Author

@thealphanerd told me to target 4.x, and there is no open staging branch I can found.

@mscdex
Copy link
Contributor

mscdex commented Nov 18, 2016

Hrmm... I was under the impression v4.x-staging/v6.x-staging/v7.x-staging were still being used for backports...

@sam-github sam-github closed this Nov 18, 2016
@MylesBorins
Copy link
Contributor

sorry for the miscommunication

@sam-github we target the staging branches for all backports as mentioned by @mscdex

@sam-github sam-github deleted the v4-pr/9032 branch April 17, 2017 20:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

c++ Issues and PRs that require attention from people who are familiar with C++.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants