I have to admit that I haven't used checksums yet but considering the data someone enters in a web browser (passwords, PINs, ...) it surely makes sense to verify checksums if you download the binary from a server different from the main server.

As long as there is no protocol or html-construct for checksums I don't see a way to implement it easily. One idea would be to automatically point from mirrored downloads to the main source where the browser can automatically fetch the checksum to be able to verify it against the downloaded copy from the mirror site. I don't know whether a concept like this already exists.

Live checking (while the file is downloaded) might be quite complicated, because paused downloads have to be considered separatly and other issues have to be taken into account. Therefore I think a contextual menu item which calculates the md5 checksum and puts it on the clipboard might be the best solution.

As already has been mentioned in bug 101743 there are more checksums than md5, the question would be: which one to implement? md5 is included with Mac OS X so there's no need to put the algorithm into Camino and from what I know MD5 is the one used most (although surely not the best one around).

Cheers,

  Martin
_______________________________________________
Camino mailing list
[email protected]
http://mozdev.org/mailman/listinfo/camino

Reply via email to