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?
------------------------------------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
_______________________________________________
S3tools-general mailing list
S3tools-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/s3tools-general

Reply via email to