Quote:
Originally Posted by pghaworth
Wonder if it's related to the 5.4.5.1 update file? Mildly corrupted in some small way or something.
|
The possibility of that happening is extremely, extremely, slim.
Every bit of the package is included in a one-way, crypto, hash and the hash is crypto signed.
As NiLuJe pointed out in a reply to another of my posts, the package's headers are not included in the signed hash.
But the most likely result of changes to the headers is the package would be refused by the installer (fail internal consistency checks).