Skip to content

Conversation

@vcsjones
Copy link
Member

@vcsjones vcsjones commented Jan 22, 2025

This provides an implementation of AesGcm in 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 of AesGcm because it was included in .NET Standard 2.1 with an API shape that we do not want to support.

Closes #89718

@bartonjs
Copy link
Member

The code refactorings LGTM; signoff withheld pending resolution of the "fail the build" target.

@bartonjs bartonjs requested a review from ViktorHofer January 27, 2025 19:21
@vcsjones vcsjones marked this pull request as ready for review January 27, 2025 20:43
Co-authored-by: Jeremy Barton <[email protected]>
@vcsjones vcsjones added this to the 10.0.0 milestone Feb 14, 2025
@vcsjones
Copy link
Member Author

Okay, AesGcm is no longer present in .NET Standard builds.

.NET 10 (type forward):

Screenshot 2025-02-14 at 9 38 17 AM 1

.NET 9 (type forward):

Screenshot 2025-02-14 at 9 41 19 AM

.NET 8 (type forward):

Screenshot 2025-02-14 at 9 41 56 AM

.NET Framework (implementation):

Screenshot 2025-02-14 at 9 40 00 AM

.NET Standard (no AesGcm)

Screenshot 2025-02-14 at 9 42 57 AM

@vcsjones
Copy link
Member Author

Failures are known and unrelated to the changes. Merging.

@vcsjones vcsjones merged commit 09c5809 into dotnet:main Feb 14, 2025
83 of 87 checks passed
@vcsjones vcsjones deleted the outbox-aes-gcm branch February 14, 2025 21:44
@github-actions github-actions bot locked and limited conversation to collaborators Mar 17, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[API Proposal]: Provide an implementation AesGcm in Microsoft.Bcl.Cryptography

5 participants