Standard: Consider adding AesGcm to .NET Standard 2.1

[alecgn]

[bartonjs]

AesManaged has no good reason to exist in .NET Standard; you should just replace any usage of it with Aes.Create() and just use the Aes base class.

[terrajobst]

Thanks @bartonjs. In that case, I believe we shouldn't be adding this.

[bartonjs]

I'm a little confused by the edit history, since I feel like when I commented it said AesGcm and AesManaged (maybe I only read the email description I got).

AesCcm and AesGcm would be reasonable (https://github.com/dotnet/corefx/pull/31389)

[terrajobst]

@alecgn could you clarify which types you're looking for?

[alecgn]

@bartonjs @terrajobst in a first moment I suggested both AesManaged and AesGcm; however, after looking the source code, I actually realized that Aes.Create() should be used in place of AesManaged, so I edited this and deleted the AesManaged part. But for now, I'm looking for AesGcm, and like @bartonjs suggest, AesCcm would be great too.

[terrajobst]

Thanks @alecgn, I've sumitted #1326 to expose these two types.

[alecgn]

Thanks a lot guys, that's great! ;)

[alecgn]

A silly doubt, these types will be available in the next .NET Core 3 preview release right?

[bartonjs]

@alecgn Yep, they've been in since before 3.0 Preview 1 (https://devblogs.microsoft.com/dotnet/announcing-net-core-3-preview-1-and-open-sourcing-windows-desktop-frameworks/).