SHA1 mismatch Win95?

Hi,
Is it me doing something wrong, or is the given SHA1 different from either
Microsoft Windows 95B (4.00.1111) (OSR2) [English] (CD).7z (downloaded file SHA1: e2bf0612528f812e0cd5436a59e1a8c6e012ad2f)
or
windows95b.iso (downloaded file SHA1: c5684b0eb2428e033db8e6fe0d2075d0c4631fc9)?

Comments

  • By the way, just checked Windows 95 OSR 2.5 (OEM) (ISO) as well:
    SHA1 site: 26c39dc59265c38b4fc39d38755e34c3b54b1934
    my sha1 : 0ca7666647c52850918d0b031d2b57553886e674 (.iso)
    26dd8c65cb4fdd38755e34f54b1934914225765d (.7z)

  • @heller73 This is a known issue. The files are fine, but the hashes were somehow corrupted in the database.

  • @Totengeist said:
    @heller73 This is a known issue. The files are fine, but the hashes were somehow corrupted in the database.

    This is 2018, sites get hacked, isp's use deep packet inspection to redirect to malicious versions of legitimate programs, etc. Besides, what is the point of showing sha1's on the site which are not correct anyways? For me, I'd for now steer clear of downloading binaries which not entirely tick all the boxes of "fine". On the other hand, keep up the good work, some room for improvement I guess.

  • I keep meaning to regenerate them. My suspicion is that the SHAs were generated before post-processing.

Sign In or Register to comment.