| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Perhaps we should also note that this particular chacha20-poly1305 implementation conforms to RFC 7539 (IIRC)? |
Sorry, something went wrong.
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. |
Sorry, something went wrong.
Sorry, something went wrong.
@mscdex #42370 adds it to the existing mentions of chacha20-poly1305. |
Sorry, something went wrong.
|
Rebased without changes. |
Sorry, something went wrong.
Sorry, something went wrong.
|
Thanks for reviewing! |
Sorry, something went wrong.
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>
| Back | FazBrowse Home | New Git URL |
The crypto documentation does not list chacha20-poly1305 as a supported AEAD algorithm and omits that the algorithm requires passing the authTagLength option.
This patch changes that and also adds a test to assert that the documented behavior is correct.
Arguably, chacha20-poly1305 should not require the authTagLength option. I'll probably open a separate semver-minor PR to address that and update the documentation accordingly.