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

Cyberduck trac at trac.cyberduck.io
Thu May 21 21:20:00 UTC 2015


#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 dkocher):

 Replying to [comment:17 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?
 We do this educated guess using the regular expression match as we do like
 to have checksums to verify integrity of file transfers. It is just too
 bad that you have chosen to create a ID that looks like an MD5 but is not.
 We will possibly need to disable this by default for WebDAV.

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


More information about the Cyberduck-trac mailing list