-
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
doc,test: clarify ChaCha20-Poly1305 usage #42323
doc,test: clarify ChaCha20-Poly1305 usage #42323
Conversation
Perhaps we should also note that this particular chacha20-poly1305 implementation conforms to RFC 7539 (IIRC)? |
Ideally, yes, but I haven't figured out where to best put that information without duplicating it across all relevant functions. Suggestions welcome, otherwise, I think we'll have to gradually improve the documentation over time. |
@mscdex #42370 adds it to the existing mentions of |
d1bbf33
to
0307193
Compare
Rebased without changes. |
This comment was marked as outdated.
This comment was marked as outdated.
Landed in 6559261 |
Thanks for reviewing! |
PR-URL: #42323 Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: nodejs#42323 Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #42323 Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: nodejs#42323 Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #42323 Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #42323 Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #42323 Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #42323 Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: nodejs/node#42323 Reviewed-By: James M Snell <jasnell@gmail.com>
The crypto documentation does not list
chacha20-poly1305
as a supported AEAD algorithm and omits that the algorithm requires passing theauthTagLength
option.This patch changes that and also adds a test to assert that the documented behavior is correct.
Arguably,
chacha20-poly1305
should not require theauthTagLength
option. I'll probably open a separate semver-minor PR to address that and update the documentation accordingly.