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.

Sign up for GitHub

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

Jump to bottom

SSE-C encryption broken for Exists/Attributes call #141

Open
jabbrwcky opened this issue Sep 26, 2024 · 1 comment · May be fixed by #142
Open

SSE-C encryption broken for Exists/Attributes call #141

jabbrwcky opened this issue Sep 26, 2024 · 1 comment · May be fixed by #142

Comments

@jabbrwcky
Copy link

jabbrwcky commented Sep 26, 2024 •
edited
Loading

Hi,

I configured thanos to use SSE-C for encryption.

In contrast to SSE-KMS and default SSE the client has to pass the key for the request, which currently is missing for Exists() and Attributes() method of the S3 client.

PR: #142
@jabbrwcky jabbrwcky mentioned this issue Sep 26, 2024
Open
@jabbrwcky jabbrwcky changed the title SSE-C encryption broken for Exits/Attributes call SSE-C encryption broken for Exists/Attributes call Sep 26, 2024
@dagobertdocker
Copy link

Thanks for this PR! I'd love for this to be merged, my provider is using SSE-C and I cannot use Thanos because of the underlying issue.

@jabbrwcky jabbrwcky linked a pull request Oct 14, 2024 that will close this issue
Open
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Pass server-side encryption option to minio.StatObject call jabbrwcky/objstore
2 participants
@jabbrwcky @dagobertdocker