(imported topic written by SystemAdmin)
Is anyone else continuing to have SHA1 hash mismatches on content provided by IBM? The McAfee Stinger fixlets are notoriously never correct and it seems like the Windows 7 Compatibility site within BigFix labs is also a problem. The Stinger fixlets haven’t worked in about a month. We’ve tried them the same day they were released and still had the issue.
(imported comment written by JasonHonda)
This is a constant battle for us, at least with the AV content in CMEP because we are subject to the policies the AV vendor uses for the downloads of the definitions. If they do not keep around older versions, and update extremely frequently then it is very hard for us to get published content out that is valid for very long before they update again.
It is good to bring it to our attention though as we can take a look to see if we are missing another way. Example here is Stinger, a little while back, McAfee changed the download to no longer be versioned and that meant as soon as they updated, our content would not longer be correct. At the time we could not find another location of the previous versions but a check now, makes me think we can find a way so I’ll file that bug and get it fixed so hopefully the fixlet links stay active a little longer.
I’ll ask around about the mismatch in labs also.
(imported comment written by SystemAdmin)
I saw the same issue with the Adobe Reader in the version 9.x (cannot recall exactly). It appears that Adobe would use the same file name and URL for different versions. So we had the sha1 or file size failed. Personally, I blame Adobe for that one as Adobe has always had “challenging” installers 
Martin Carnegie
Gulf Breeze Software Partners
(imported comment written by SystemAdmin)
It should be fixed now with the latest version of the site (v 21).