MX-23.1 ISO Checksums don't match [Solved]

[Mauser]

I first downloaded MX-23.1 Xfce November and the checksums didn't match. I tried it 3 times figuring 3 times would be a charm and each time they didn't match. Then I downloaded the October release from here https://mxlinux.org/blog/mx-23-1-libretto-released/ and the checksum didn't match on that one either. What's up with that?

[Mauser]

The MX-23.1 November ISO shows

md5: 93d9c0e49741fbca0fc8181236968a01

sha256: 13593f36ffedc38fece807098e950ab437c26c850806cf79b6aeb72a1dd7621

As for the Sig. file it's

MD5: 86f1329219b0b4b8efe38a3a01c62fba

SHA256: f2e1a1a0de297456cf8207ad52a564e6323e003493bd05bbf3ba40fea0c6a0ba

As you can see they don't match and no matter if I download the October release or November release they never match or how many times I download an ISO. There is something seriously wrong with the MX downloads from Sourceforge that I hope is looked into. I hope everyone checked the download of the MX ISO.

[dolphin_oracle]

I’m looking into it. Can confirm problem with downloading the November snapshot. The October checksums for the xfce release looked ok.

[dolphin_oracle]

I haven't checked all the october official release isos, but the download of the october 23.1 Xfce iso appears to be OK.

[fehlix]

The November checksum calculated by sourceforge
do all match to the iso-, sig- and sha516-files
And the sig and sha256-files do match and verified by signature.
The only file missing is the sig for the November Xfce iso.
And yes... The MX-23.1_November_x64.iso.sig is also there...
to performe signature validation check -> see wiki

[Adrian]

The MX-23.1 November ISO shows

md5: 93d9c0e49741fbca0fc8181236968a01

sha256: 13593f36ffedc38fece807098e950ab437c26c850806cf79b6aeb72a1dd7621

As for the Sig. file it's

MD5: 86f1329219b0b4b8efe38a3a01c62fba

SHA256: f2e1a1a0de297456cf8207ad52a564e6323e003493bd05bbf3ba40fea0c6a0ba

As you can see they don't match and no matter if I download the October release or November release they never match or how many times I download an ISO. There is something seriously wrong with the MX downloads from Sourceforge that I hope is looked into. I hope everyone checked the download of the MX ISO.

The md5 and sha256 are correct (although we provide none of these files, I provide only the .sha512 and the .sig files for the ISO)

I don't understand what are you doing, do you compare the MD5 of the .iso with the MD5 of the .sig file? Those are not meant to match.

I recommend suing this command to check if the checksum is correct (you need .iso and .sha512 in the same folder):

Code: Select all

sha512sum -c MX-23.1_November_x64.iso.sha512

Or check the .sig directly (which implicitly does a checksum too besides verifying who signed the ISO -- namely me):

Code: Select all

gpg --verify MX-23.1_November_x64.iso.sig

[dolphin_oracle]

@Mauser if you are using the thunar right-click on iso action to calculate the checksums, the value calculated is a sha256 not the sha512 that adrian has provided in the file. I missed that. the files I downloaded all pass the 512 check.

if you right click the sha512 file then you will get an option to verify integrity. you can use that, it will give you a pass or a fail. the sha512 file and the iso must be in the same directory.

the november snapshots appear fine.

[MXRobo]

Also, Gtkhash>Edit>Preferences.

[Mauser]

I haven't checked all the october official release isos, but the download of the october 23.1 Xfce iso appears to be OK.

I re-downloaded the October ISO and this time the Checksums matched. Thanks. Sorry it took so long to reply because I was busy installing MX-23.1 and setting things up also restoring my backup files to the new MX version.

[Mauser]

The November checksum calculated by sourceforge
do all match to the iso-, sig- and sha516-files
And the sig and sha256-files do match and verified by signature.
The only file missing is the sig for the November Xfce iso.
And yes... The MX-23.1_November_x64.iso.sig is also there...
to performe signature validation check -> see wiki

Strange because my post above showed it didn't match after downloading 4 copies.