Updating CryptographyAESKey::encrypt
to generate 96 bit IVs for GCM block cipher mode to adhere to JWA RFC
#355
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.
Updating
CryptographyAESKey::encrypt
to generate 96 bit IVs for GCM block cipher mode to adhere to the RFC for JWA injose/backends/cryptography_backend.py
See https://www.rfc-editor.org/rfc/rfc7518.html#section-5.3 for the official RFC requirements for JWA
See panva/jose#678 for related discussion on this issue
Testing done
Ran the following commands, which successfully built the package and passed all unit tests that were not already failing: