Issues with aws s3 sse-c, getting strange log entries and errors

[ncw (Nick Craig-Wood)]

@asdffdsa

did more testing, seems that aws did encrypt the file.

Great

@asdffdsa

now the problem is that

• rclone does not compare checksum on upload/download.
• rclone check cannot compare

What I can do is add metadata, the same as we do for large files with the md5sum of the decrypted data. This will enable checksums to be compared and rclone check to work. If you want to see how that would work, try uploading a file with --s3-upload-cutoff 0. Rclone will add a header (this is a base64 encoded md5 checksum)

X-Amz-Meta-Md5chksum: JeMXdz8wjkRsyExQOm0fhQ==

Is that worth doing do you think?

@asdffdsa

also, seems that s3.browser set these headers, the second value is the sha256 of the

Interesting... I don't think that is standardised though - as in it is just what s3.browser does.