Merged
Conversation
16c40f3 to
4e627d3
Compare
d1e66bf to
aea5975
Compare
aea5975 to
83cda47
Compare
Contributor
Author
|
Hi @reaperhulk, just making sure you got this one. |
reaperhulk
approved these changes
May 6, 2025
Member
|
Thanks for your patience here, life things have me operating with very limited bandwidth for open source right now! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hey @reaperhulk,
Included low level bindings for newer APIs for AEAD AES-based constructs (
crypto_aead_aegis*from 1.0.19), plus oldcrypto_aead_aes256gcm*.With
crypto_aead_aegis*(with AES-NI) I noticed a decent performance bump compared with related AES GCM based constructs fromcryptography.Would be a nice addition for the next release, keeping up to date with the latest libsodium versions.