DobarParshut wrote:hi guys, sorry for bothering..
i may be a noob, but i can't solve this one.. i upgraded my pc to windows 10, and before that i did a backup of my old cod games.. now i copied the files from player2 file and put the into newly installed mw3, but when i login with my username, all my classes and data aren't available.. am i doing something wrong or how can i import old game files to a clean install of mw3?
szczurcio wrote:Stop capitalizing nouns dude, this ain't German
DobarParshut wrote:so, basically, there is nothing to do
anyway, thanks guys!
~Seraphim wrote:DobarParshut wrote:so, basically, there is nothing to do
anyway, thanks guys!
Well if you want to get technical, the stats files were encrypted with a rather weak algorithm ( if you can even call that an algorithm ) so you can _technically_ brute force the decryption.
Basically there's 2^32 possible combinations you can try.
Read this to find out how stats files were encrypted. You can decrypt them by simply running it through the decryption function with every possible lower SteamID ( 00000000 - FFFFFFFF )
Hyper-V wrote:FWIW, I'll leave what I found out after I quickly glanced over the code, in case anybody decides to do this:
1. The function you're targeting is SteamDataCrypto (steam_api_emu_misc.cpp)
2. The encryption function seems like a stream cipher, so both encryption and decryption use the same function (TL;DR stream ciphers generate a bunch of values based on the key and then usually XOR the input against that, so generating the same values and XORing again decrypts the encrypted data)
3. The implementation is... laughable, without being too mean. I recommend rewriting it if your goal is to attack the crypto, for several reasons; one of them being the "if", which can be dumbed down to a single expression, which could help analyzing the function. (branches are never nice when translating crypto code to math)
4. There is a side-channel attack which, in the worst case, reduces the key space to ((2**32 - 1) / 4). However, in practice, the actual keyspace is reduced to less than 5% of the worst case scenario, making this concrete example extremely easy to crack. However, I'll leave that as an exercise to the reader. :-)
Users browsing this forum: No registered users and 11 guests