fixes #12837 - make AES-GCM tag length configurable #12838
Closed
Conversation
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
eqvinox
force-pushed
the
aes-gcm-tag-len
branch
2 times, most recently
from
f613821 to
011398f
Compare
Valid AES-GCM tag lengths as per NIST 800-38D, default is 16 (which is also backwards compatible.). Signed-off-by: David Lamparter <[email protected]>
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.
Valid AES-GCM tag lengths as per NIST 800-38D, default is 16 (which is also backwards compatible.).
I don't see any further requirements from
CONTRIBUTING.rst, do I need to do something else? I'm not sure about linters/stylecheckers/…