fix: handle S3 server encoding of non-US-ASCII object metadata #375
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.
Issue #, if available:
Description of changes:
See aws/amazon-s3-encryption-client-go#56 for more details.
The AWS SDK for Java v2 does not allow use of non-US-ASCII characters. However, since it is the most fully-featured and widely-used implementation of the S3 Encryption Client, it should be able to decrypt ciphertexts which other clients can write.
This PR adds support for reading/decrypting messages which have non-US-ASCII characters in the encryption context/material description by decoding the S3 server's unique encoding scheme.
This PR also adds a simple "test vector" bucket which contains static ciphertexts to decrypt as part of integration testing, as the Java client cannot write the ciphertexts that it can now decrypt.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Check any applicable: