On Mon, May 20, 2013 at 11:17 AM, William Smith <w_smith@compusmiths.com> wrote:
I assume this version for sorting out MD5SUM is going to be in the new release?


On Oct 17, 2012, at 12:04 PM, Matt_Domsch@Dell.com wrote:

> If the file is bigger than the chunk size, you’ll need a version (e.g. from my github merge branch) that stores the real MD5SUM in the metadata, rather than relying on the S3 ETag, which is incorrect if using it to compare the whole file – the S3 ETag only is correct for a single chunk of the file.

Yes, these patches are in 1.5.0-alpha already.