- I RaveN I
- |
- Honorable Member
Last member of the i4Ni clan.
Even after like 20 topics you still don't understand server sided activation :|
How it works: h2vregistration encrypts the key somehow (probably a combination of their base 24 then character shift from halo pc and md5) and sends the hash to microsoft's servers. The key is then encrypted and then sent again with a salt sent from microsoft's servers based on the first one. If the two keys match, microsoft generates a (let's call it) keyhash based on the key you sent and their own algorithm, and stores that key's number of uses/activation in their own database. The keyhash is then encrypted and stored in token.bin. Each time you attempt to sign into live or join a server, your keyhash is decrypted then sent to microsoft where it is compared against some encrypted form of your key or the other way around, and if it is valid you are allowed to sign into live/the server. If it is invalid, your connection is rejected and you're forever alone.
Without a cracked server and live master server replacement, it's impossible to get online even if you did have a cracked h2v.
Which brings me to another point. I decided to run dllexp on MF.dll to find out what's in it (the "cracked" one) and here's what I've found:
[code]MFCreateAudioRendererActivate 0x10001599 0x00001599 1 (0x1) MF.dll
MFCreateSourceResolver 0x1000159f 0x0000159f 3 (0x3) MF.dll
MFCreateTopology 0x10001595 0x00001595 4 (0x4) MF.dll
MFCreateTopologyNode 0x1000159d 0x0000159d 5 (0x5) MF.dll
MFCreateVideoRendererActivate 0x1000159b 0x0000159b 6 (0x6) MF.dll
MFGetService 0x100015a1 0x000015a1 7 (0x7) MF.dll
[/code]
To make that a little clearer, the first column is the undecorated export name, the second is the expected address when loaded in memory, the third is the offset from MF.dll's base address, and the last is the ordinal number (export number)
So now let's remember that Media Foundations is intended as a replacement for DirectShow, a graphics pipeline. Now let's go look up some of those functions on MSDN. Here's the main page of the SDK.
And lol, just dissassembling it and found some interesting stuff. Brb.