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

Users want client-side encryption for Google Cloud Storage. #1451

Closed
SurferJeffAtGoogle opened this issue Sep 14, 2017 · 4 comments
Closed
Assignees
Labels
api: storage Issues related to the Cloud Storage API. priority: p2 Moderately-important priority. Fix may not be included in next release.

Comments

@SurferJeffAtGoogle
Copy link
Contributor

No description provided.

@SurferJeffAtGoogle SurferJeffAtGoogle added the api: storage Issues related to the Cloud Storage API. label Sep 14, 2017
@jskeet jskeet added the priority: p2 Moderately-important priority. Fix may not be included in next release. label Sep 20, 2017
@jskeet jskeet self-assigned this Sep 20, 2017
@jskeet
Copy link
Collaborator

jskeet commented Oct 19, 2017

Do we have more information about this - a precise set of requirements? It'll be hard to do any work on it otherwise.

@jskeet
Copy link
Collaborator

jskeet commented Dec 6, 2017

Closing for now having added this to the backlog

@jskeet jskeet closed this as completed Dec 6, 2017
@SurferJeffAtGoogle
Copy link
Contributor Author

The client needs to do envelope encryption and store the KEK, IV, and KML key url in the file metadata. The backlog seems like a good home for this feature request.

@amanda-tarafa
Copy link
Contributor

This is being evaluated across client libraries.
Removing from backlog.

amanda-tarafa added a commit to amanda-tarafa/google-cloud-dotnet that referenced this issue Nov 19, 2020
amanda-tarafa added a commit that referenced this issue Nov 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: storage Issues related to the Cloud Storage API. priority: p2 Moderately-important priority. Fix may not be included in next release.
Projects
None yet
Development

No branches or pull requests

3 participants