[Cyberduck-trac] [Cyberduck] #8798: MD5 checksum failure for downloads

[Cyberduck]

#8798: MD5 checksum failure for downloads
-----------------------------+---------------------------
 Reporter:  anonymous        |         Owner:  dkocher
     Type:  defect           |        Status:  closed
 Priority:  normal           |     Milestone:  4.8
Component:  webdav           |       Version:  4.7
 Severity:  normal           |    Resolution:  thirdparty
 Keywords:  md5, hash, etag  |  Architecture:  Intel
 Platform:  Windows 7        |
-----------------------------+---------------------------

Comment (by samottenhoff):

 > However, if the ETag returns matches [a-fA-F0-9]{32} we assume it is a
 MD5.

 r17479 assumes that if it sees a 32-character ETag, that it is an MD5
 calculated using a certain formula for checksum verification. But there is
 no specification that dictates how the ETag should be calculated. Sakai
 just happens to use a 32-character ETag. Why is r17479 assuming that our
 ETag should be used for checksum verification?

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