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

Cluster resources are not encrypted in Object Storage #559

Open
mckaymic opened this issue Aug 5, 2020 · 2 comments
Open

Cluster resources are not encrypted in Object Storage #559

mckaymic opened this issue Aug 5, 2020 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@mckaymic
Copy link
Contributor

mckaymic commented Aug 5, 2020

When posting data to a cluster, the objects should be encrypted with the org key when upload to Object Storage.

await req.s3.createBucketAndObject(bucket, `${keyHash}/${searchableDataHash}`, dataStr);

async encryptAndUploadFile(bucketName, path, fileStream, encryptionKey, iv=null){

@mckaymic mckaymic added the bug Something isn't working label Aug 5, 2020
@rmgraham rmgraham self-assigned this Aug 12, 2020
@dalehille
Copy link
Contributor

@rmgraham can you check if the code for this one is merged? I might have this mixed up with another issue but I think this one was related to #559 . But stalebot closed 559 which may have given us the impression that this issue was resolved.

@dalehille dalehille reopened this Feb 14, 2021
@carrolp
Copy link
Contributor

carrolp commented Sep 30, 2022

User can choose which resources and how much of the resources should be sent to razeedash-api (e.g. just secret metadata, not values). An encrypting datastore such as S3 can also be used. This is a reasonable enhancement, but not a high priority.

@carrolp carrolp added enhancement New feature or request and removed bug Something isn't working labels Sep 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants