Encryption doesn't work (/t/rclone-to-minio-behind-nginx/24068/3 ticket).
Following up a confirmed issue from the ticket above: how do I work around that, to keep my backup encrypted?
Unfortunately, my original ticket was closed (with a prompt and correct advice - thank you very much! I just had to remove both server_side_encryption and sse_kms_key_id), so I'm opening a new one, to ensure I can keep my backups safe.
The minio docs say it does support SSE
https://docs.min.io/docs/minio-security-overview.html
I wonder if the version you are using doesn't support it though?
The alternative would be to use the crypt backend and get rclone to do the encryption
The very latest one. The only thing is that’s it running behind nginx (on Cloudron) - could it be the issue? If so, any ideas how to work this out?
Thanks for crypt backend, I would keep it as a plan B, in case the main won’t work.
Not sure...
Do the aws tools work with it using sse-c?
Don’t know - how do I check that?
There is a walkthrough in the minio docs
https://docs.min.io/docs/how-to-use-minio-s-server-side-encryption-with-aws-cli.html
Apologies, I need a bit more time to test that.
hi,
i have used sse-c with amazon s3 and wasabi, a s3 clone.
rclone sse-c support should work with minio.
i use both rclone crypt and sse-c encryption at the same time.
use a rclone crypted remote to encrypt the folder/file names and sse-c to crypt the contents of the files.
[sse]
type = s3
provider = Wasabi
access_key_id =
secret_access_key =
endpoint = s3.us-east-2.wasabisys.com
sse_customer_algorithm = AES256
sse_customer_key =
[ssectest]
type = crypt
remote = sse:ssectest
password =
password2 =
filename_encryption = standard
directory_name_encryption = true
crypt_no_data_encryption = true
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.