This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox 18.0.2 installer's checksum is different from mozilla.org and mozilla.com, even though files are same length.

  • 1 reply
  • 9 have this problem
  • 1 view
  • Last reply by frucade

more options

Shortly after installing Firefox 18.0.2 on a Windows 7 system, Firefox aborted and had to be restored ("Well this is embarassing..."). I uninstalled 18.0.2 using the Windows "Programs and Features" controller.

I then downloaded the 18.0.2 installer from www.mozilla.com, which re-directed me to "http://www.mozilla.org/en-US/firefox/new/", which I saved to my Desktop as "18-0-2_com". Windows complained that the file was not safe, although the most current version of Norton Internet Security, version 19.9.1.14, judged the file to be safe. When I ran the installer, Windows said the file was corrupt and stopped the installation.

Next, I went to www.mozilla.org, which re-directed me to a different site, "http://www.mozilla.org/en-US/products/download.html?product=firefox-18.0.2&os=win&lang=en-US". I saved the file as "18-0-2_org". Windows did not complain about the safety of this file, and it installed Firefox 18.0.2 without incident.

Since I run Cygwin 1.7.11-1, I was able to run the cksum command on both installer files. Here are the results:

Source Local file name File length CRC cksum


mozilla.com 18-0-2_com 20300952 3466106289 mozilla.org 18-0-2_org 20300952 1844093656

Although both installers have the same length, they differ in content; consequently, the checksums differ. It appears that 18-0-2_com is corrupt, while 18-0-2_org is not. Since the two files come from different locations, it seems that one has been accidentally or intentionally altered. Since the file lengths are the same, I am suspicious that the corrupted file has been made to look like the uncorrupted file, so that the number of bytes in both files is identical. This suggests that the corruption was deliberate.

Shortly after installing Firefox 18.0.2 on a Windows 7 system, Firefox aborted and had to be restored ("Well this is embarassing..."). I uninstalled 18.0.2 using the Windows "Programs and Features" controller. I then downloaded the 18.0.2 installer from www.mozilla.com, which re-directed me to "http://www.mozilla.org/en-US/firefox/new/", which I saved to my Desktop as "18-0-2_com". Windows complained that the file was not safe, although the most current version of Norton Internet Security, version 19.9.1.14, judged the file to be safe. When I ran the installer, Windows said the file was corrupt and stopped the installation. Next, I went to www.mozilla.org, which re-directed me to a different site, "http://www.mozilla.org/en-US/products/download.html?product=firefox-18.0.2&os=win&lang=en-US". I saved the file as "18-0-2_org". Windows did not complain about the safety of this file, and it installed Firefox 18.0.2 without incident. Since I run Cygwin 1.7.11-1, I was able to run the cksum command on both installer files. Here are the results: Source Local file name File length CRC cksum -------------------------------------------------------------------------------------------------------------------------------- mozilla.com 18-0-2_com 20300952 3466106289 mozilla.org 18-0-2_org 20300952 1844093656 Although both installers have the same length, they differ in content; consequently, the checksums differ. It appears that 18-0-2_com is corrupt, while 18-0-2_org is not. Since the two files come from different locations, it seems that one has been accidentally or intentionally altered. Since the file lengths are the same, I am suspicious that the corrupted file has been made to look like the uncorrupted file, so that the number of bytes in both files is identical. This suggests that the corruption was deliberate.

All Replies (1)

more options

I tried to download the FireFox setup from both locations you mentioned. I could not reproduce your problem. Always the same file with the same MD5 hash:

 C:\tmp>md5sum "Firefox Setup 18.0.2.exe
 181ac7211db54e793845e8c7216c1a8b *Firefox Setup 18.0.2.exe

Is it still reproducible from your location? Where are you located?