Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AmazonS3EncryptionClient cannot decrypt 'AES/GCM/NoPadding' SES messages #748

Closed
mjdaly opened this issue Sep 13, 2017 · 2 comments
Closed
Assignees
Labels
guidance Question that needs advice or information.

Comments

@mjdaly
Copy link

mjdaly commented Sep 13, 2017

AmazonS3EncryptionClient cannot decrypt SES messages stored in S3.

Expected Behavior

AmazonS3EncryptionClient decrypts encrypted S3 objects created by SES.

Current Behavior

AmazonS3EncryptionClient throws an exception indicating the decryption method is not supported:

'AES/GCM/NoPadding' for metadata key 'x-amz-cek-alg' is invalid. AmazonS3EncryptionClient only supports 'AES/CBC/PKCS5Padding' as the content encryption algorithm. Although this mode is supported by other AWS SDKs, the .NET SDK does not support it at this time.

Context

We want to use SES for receiving emails. Emails should be encrypted at rest.

@vellozzi
Copy link
Contributor

AES/GCM/NoPadding is available in .NET 3.5 and .NET 4.5, but not .NET Core 1.0.
This has been added to our feature request list.
Note that we won't be able to implement it in the .NET Core 1.0 SDK.

I'm closing the issue, but feel free to comment.

@diehlaws diehlaws added guidance Question that needs advice or information. and removed Question labels Jan 3, 2019
@mcblair
Copy link

mcblair commented Aug 5, 2019

@vellozzi What about the .NET Core 3.0 SDK? Does dotnet/corefx#31389 allow your teams to implement this? Can the community?

@mjdaly have you solved this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
guidance Question that needs advice or information.
Projects
None yet
Development

No branches or pull requests

5 participants