search

s3fs-fuse / s3fs-fuse

FUSE-based file system backed by Amazon S3
GNU General Public License v2.0
8.65k stars 1.02k forks source link

Client-side encryption #718

Open JamesB7 opened 6 years ago

JamesB7 commented 6 years ago

Hello,

Could you please consider supporting client-side encryption? ( https://docs.aws.amazon.com/general/latest/gr/aws_sdk_cryptography.html ) This would allow not sharing the encryption keys with Amazon.

Thank you!

James

sqlbot commented 6 years ago

Note that client-side encryption is not actually a feature of the S3 service itself -- it's actually a feature provided by a subset of the official AWS SDKs, none of which are used by s3fs-fuse.

maximpichler commented 6 years ago

Even though it's not an S3 feature, it would be very useful. Or are there other ways to do this?

gaul commented 5 years ago

An s3fs fork implements this:

https://github.com/hellochrisyou/S3FS_OpenSSL_RC4_MD5

However I think we should align with the AWS implementation to allow interoperability:

https://github.com/gaul/s3proxy/pull/296#issuecomment-530817114

jopdorp commented 2 years ago

client side encryption would be a great feature.

rebelga commented 1 year ago

It's a big issue for me and why I can't use this currently. Without client side encryption, my data would be too exposed. Interoperability with AWS S3 SDK is not at all important to me, just S3FS interoperability across S3 providers.

gaul commented 1 year ago

@rebelga You can work around this with S3Proxy using the encryption middleware: https://github.com/gaul/s3proxy/pull/398. As for s3fs itself, I think it should follow the AWS style for interoperability.