mentioned several times... but never explained in detail

In fact, the checksum is a simple md5 added to the original encrypted file, and therefore we can add as many md5s as we want at the end and make believe that the file is valid.

igoview by assuming that on some extensions the md5 is still existing and sometimes mistakenly considers that the last 16 bytes read are an erroneous MD5,

except for a good estimate it is necessary to analyze the beginning of the file to extract the supposed position of the end of the file.

This value less than or equal to the size of the file, is sometimes followed by a zip archive which once eliminated allows access to the MD5 signature if the resulting value corresponds to the size of the file - 16 bytes.

By ignoring these 16 bytes, it then becomes possible to calculate the real md5 to compare it to the existing one or possibly add it as a verification signature.

So if igoview displays: a green flag means that the md5 corresponds to the file as long as it has not been modified upstream, a red flag will not necessarily mean that the file is corrupt.

we have already observed aberrations of itineraries by off-road lines because the data of the file was incorrect while its structure was good.