From: Abrao G. <ab...@ya...> - 2014-04-22 16:41:28
|
Using the s3cmd version 1.5.0-beta1, I receive a "MD5 signatures do not match" when downloading a file (no multipart involved) that was previously uploaded with GPG encryption. It seems that the problem is caused by line 1026 in S3.py replacing the etag md5 value with the md5 value from s3cmd-attrs, which is the md5 before file encryption. Could somebody please take a look at it? |