{{ message }}
Add CSEK decryption for storage.get(BlobId,..)#5882
Merged
Conversation
googlebot
added
the
cla: yes
frankyn
added
api: storage
JesseLovelace
approved these changes
Jul 29, 2019
Contributor
Author
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
3 participants
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.
Hi @JesseLovelace,
Could you take a look at this fix for an internal customer request: b/79339975.
Currently storage.get() doesn't support decrypting object crc32c and md5 using CSEK. When objects are encrypted using CSEK, md5 and crc32c are also encrypted. Without supporting the option to decrypt it blocks this specific use-case.
For more information: https://cloud.google.com/storage/docs/encryption/customer-supplied-keys#encrypted-elements