-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
crypto: improve setAuthTag #22538
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
crypto: improve setAuthTag #22538
Conversation
This is an attempt to make the behavior of setAuthTag match the documentation: In GCM mode, it can be called at any time before invoking final, even after the last call to update. Fixes: nodejs#22421
Ping @nodejs/crypto |
This needs a review. No one looked at it for five days. |
Thanks, @BridgeAR. @nodejs/crypto seems to be mostly dead these days. The change itself isn't that complex: It should be possible to call |
Landed in b402609 |
resolves aws#199 In Node.js versions 10.9 and older will fail to decrypt if decipher.update is not called. nodejs/node#22538 fixes this. If the content is empty, push an empty buffer.
resolves #199 In Node.js versions 10.9 and older will fail to decrypt if decipher.update is not called. nodejs/node#22538 fixes this. If the content is empty, push an empty buffer.
This is an attempt to make the behavior of
setAuthTag
match the documentation: In GCM mode, it can be called at any time before invoking final, even after the last call to update.Fixes: #22421
cc @nodejs/crypto @nodejs/security-wg @achronos0
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes