mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #388] 'load_sse_c' option not working #205
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#205
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @soufrk on GitHub (Apr 7, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/388
I have been working with SSE-C capabilities of 's3fs', and after reading through, what I found out is a custom key can be specified at the time of mounting. What if individual files in a single bucket are encrypted with different keys. Is there a specific way to mount a bucket simply, and make download/fetch requests for a particular file with a particular key ?
Let me know, in case the problem statement is not clear.
EDIT
Additionally, just now I discovered that reading encrypted file is not working even after mounting with custom key.
Hoping so that the following command is correct for SSE-C
sudo s3fs my-own-bucket /var/s3 -o allow_other -o use_sse=custom:/etc/mykeyI would also like to add the fact the file upload(encrypt)/download(decrypt) is working fine through SDK.
EDIT
I realized that there is a 'load_sse_c' option. But I am not able to get it working. As, the syntax for it's seems to be unclear.
Tried
-o load_sse_c=/etc/mykeyand-o load_sse_c /etc/mykey, yet suffers from syntactical errors.@soufrk commented on GitHub (Apr 11, 2016):
Closing this one as posting the question directly to enhancement thread.
@soufrk commented on GitHub (Apr 11, 2016):
Reopening, as unable to get issue raised in enhancement ticket.
Unable to get 'load_sse_c' option working. Results of trials below,
Any help will be appreciated.
@ggtakec commented on GitHub (May 6, 2016):
@soufrk I'm very sorry for my late reply.
I check your pointed out problems, it has been fixed by #409
I closed this issue, but if you found a bug about this, please reopen.
Regards,