Add test vectors for AES-GCM-SIV #9930
Merged
Conversation
This file contains 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.
This PR adds test vectors for
AES-GCM-SIV, as part of #9795.The
openssl.txtfile contains test vectors lifted from the OpenSSL repo (source), which in turn are based on the vectors defined in RFC 8452.However, these vectors only test key lengths of 128 and 256 bits. In order to test 192-bit keys, we generate test vectors using OpenSSL (through cryptography) and verify them using Rust. The new vectors are based on the existing
openssl.txtvectors, except that the keys have been either extended with 0s or truncated in order to make them 192-bit (and the other dependent fields have been updated accordingly).