Outbox AesGcm in to Microsoft.Bcl.Cryptography#111722
Merged
vcsjones merged 10 commits intodotnet:mainfrom Feb 14, 2025
Merged
Conversation
vcsjones
commented
Jan 22, 2025
This was referenced Jan 23, 2025
bartonjs
reviewed
Jan 27, 2025
Member
|
The code refactorings LGTM; signoff withheld pending resolution of the "fail the build" target. |
Co-authored-by: Jeremy Barton <jbarton@microsoft.com>
Member
Author
This was referenced Feb 14, 2025
This was referenced Feb 14, 2025
bartonjs
reviewed
Feb 14, 2025
bartonjs
approved these changes
Feb 14, 2025
Member
Author
|
Failures are known and unrelated to the changes. Merging. |
This was referenced Feb 14, 2025
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 provides an implementation of
AesGcmin Microsoft.Bcl.Cryptography to allow using it in .NET Framework. If the target framework is .NET 8+, then it type-forwards to the built-in version. .NET Standard is not able to include an implementation ofAesGcmbecause it was included in .NET Standard 2.1 with an API shape that we do not want to support.Closes #89718