[Cyberduck-trac] [Cyberduck] #10371: Cyberduck incorrectly assumes ETag and MD5 are equivalent for S3

Cyberduck trac at cyberduck.io
Wed Jun 20 19:23:02 UTC 2018


#10371: Cyberduck incorrectly assumes ETag and MD5 are equivalent for S3
------------------------+-------------------
    Reporter:  rpkelly  |      Owner:
        Type:  defect   |     Status:  new
    Priority:  normal   |  Milestone:
   Component:  core     |    Version:  6.6.1
    Severity:  normal   |   Keywords:
Architecture:           |   Platform:
------------------------+-------------------
 Cyberduck assumes that the ETag returned by S3 is equivalent to the MD5
 checksum of the file's content. This is not a valid assumption. The ETag
 will only be the MD5 of the object data when the object is stored as
 plaintext or encrypted using SSE-S3. If the object is encrypted using
 another method (such as SSE-C or SSE-KMS) the ETag is not the MD5 of the
 object data. If the object was created via a multipart upload, the ETag is
 not the MD5 of the object data.

--
Ticket URL: <https://trac.cyberduck.io/ticket/10371>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows


More information about the Cyberduck-trac mailing list