I suspect that this process is actually decrypting some memory rather than hashing the save itself, the end result is that a CRC32 hash of a part of the save is extracted, then compared against.
It’s called twice, with five arguments, none of these arguments point at the save data itself, but at the 360 byte blob at the end of the save file. I’m not exactly sure how these functions work exactly - other than the fact that the one we are interested in, XLiveUnprotectData, is called in a peculiar way. GTA IV uses these functions to hash and validate its save files. Another feature set provided by the Games For Windows API is various functions for “protecting” data (hashing & validating).
0 kommentar(er)
