Allow SSE C for S3 ransomware client side encryption - #956
Open
Hashim1999164 wants to merge 1 commit into
Open
Conversation
New buckets block customer provided keys by default, which broke aws.impact.s3-ransomware-client-side-encryption. Clear the SSE-C block with PutBucketEncryption before CopyObject encryption. Fixes DataDog#946
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Fixes #946 where detonation fails on new buckets that block SSE C by default.
Before encrypting objects, call PutBucketEncryption with BlockedEncryptionTypes set to NONE so CopyObject with customer provided keys can succeed. This mirrors an attacker clearing the protection at detonation time.
Test plan