crypto: asu: add support for GCM,CCM modes in ASU#7823
Open
Akshay-Belsare wants to merge 1 commit into
Open
Conversation
Add support for AES-GCM and AES-CCM modes with 128-bit and 256-bit keys. Requests using 192-bit keys, as well as AES-GCM operations with Additional Authenticated Data (AAD) that is not a multiple of 16 bytes, will fall back to software crypto. ASU does not support copy state operations, therefore scenarios involving context copy are not supported. Signed-off-by: Bhavana Bhavanam <Bhavana.Bhavanam@amd.com>
Contributor
|
Please also add your own Signed-off-by on the patches you submit in a PR. |
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
3 participants
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.
Add support for AES-GCM and AES-CCM modes with 128-bit and 256-bit keys. Requests using 192-bit keys, as well as AES-GCM operations with Additional Authenticated Data (AAD) that is not a multiple of 16 bytes, will fall back to software crypto. ASU does not support copy state operations, therefore scenarios involving context copy are not supported.