12-04-2010 07:15 PM
I performed a md5 check on the file I downloaded from Sophos' website (savosx_72_he.dmg), but I received a different string from the one listed on the tech specs page.
I got this result: 76cbd8b25919c3fda4690f36219a1f8b
Sophos shows: 21c3c6f2d93d0843238b9575792e06ef
Someone please explain the discrepancy? I've downloaded the file twice
Thanks.
Solved! Go to Solution.
12-06-2010 05:58 AM
Hi Codex and welcome to the forum.
The checksum currently (Monday 13.55) on the downloads site check page is the same as the one you saw in the file you downloaded. So that is correct.
Where did you obtain the checksum that you mention below as 'Sophos shows', starting with 21c ?
Thanks
Sandy
12-06-2010 10:38 AM
12-07-2010 12:51 AM
The FAQ refers you to the Tech specs page (Make a note of this checksum and compare it with the checksum provided on the tech specs page) which indeed lists the "old" MD5 whereas How to check that your download is genuine – using a checksum from the Mac tools help indicates the Sophos downloads webpage as the authoritative source (Make a note of this checksum and compare it with the checksum provided in the file on the Sophos downloads webpage).
To avoid (future) confusion either the two should be kept in sync or the Tech specs should refer to the file in the on the downloads page. BTW (it has already been mentioned): Neither might satisfy the truly paranoid as both fail over a https connection.
Christian
12-07-2010 03:13 AM
I have addressed the issue over the discrepancy with the checksum, it will be rectified shortly.
I am unable to finds any reference to issues with viewing checksum over https (if that is what you mean).
If someone can point me in the right direction I will investigate.
Thanks a lot
Sandy.
12-09-2010 12:44 AM
I am unable to finds any reference to issues with viewing checksum over https (if that is what you mean).
Only two posts (now three) are found for md5 https and the one not from me is from the thread Protection against MiTM attacks?. jstash says in his second post: An MD5 published on an HTTP site (which could also be hijacked) is only sufficient for checking if a download is intact. To verify that it was actually created by Sophos, either a signature file (e.g. validating a PGP/GPG signature file) or being able to download the MD5 over HTTPS (w/ cert validation) [bold print mine] would be needed.
Christian