[Repost] SIG & MD5 Protection Remover

[jh16]

Version Release Date:
June 22 2017

Version Compiled Date: ~displayed at the bottom left of login screen~
June 22 2017

Version #
7.2.5.24414 ~Size and locations are same as 7.2.5.24367~

For 32-bit:
Download

Patched:

Size: 14,771 KB

~This info is for hex editing the exe yourself via a hex editer~

Force 32-bit Client A:
at offset 0009 AF1A replace E8 73 D9 0E 00 with
90 90 90 90 90

Force 32-bit Client B:
at offset 0009 AF21 replace 74 with
75

Custom Data Edit A:
at offset 000A 445A replace 84 with
85

Custom Data Edit B:
at offset 000A 459B replace 74 64 with
90 90

For 64-bit:

Patched:

Size: 24,287 KB

~This info is for hex editing the exe yourself via a hex editer~

Custom Data Edit A:
at offset 000B 8F86 replace 01 0F 84 with
00 0F 85

Custom Data Edit B:
at offset 000B 9165 replace 01 0F 84 with
00 0F 85

[jh16]

Version Release Date:
June 22 2017

Version Compiled Date: ~displayed at the bottom left of login screen~
June 22 2017

Version #
7.2.5.24415 ~Size and locations are same as 7.2.5.24367~

For 32-bit:
Download

Patched:

Size: 14,771 KB

~This info is for hex editing the exe yourself via a hex editer~

Force 32-bit Client A:
at offset 0009 AF1A replace E8 73 D9 0E 00 with
90 90 90 90 90

Force 32-bit Client B:
at offset 0009 AF21 replace 74 with
75

Custom Data Edit A:
at offset 000A 445A replace 84 with
85

Custom Data Edit B:
at offset 000A 459B replace 74 64 with
90 90

For 64-bit:

Patched:

Size: 24,287 KB

~This info is for hex editing the exe yourself via a hex editer~

Custom Data Edit A:
at offset 000B 8F86 replace 01 0F 84 with
00 0F 85

Custom Data Edit B:
at offset 000B 9165 replace 01 0F 84 with
00 0F 85

[jh16]

Version Release Date:
June 26 2017

Version Compiled Date: ~displayed at the bottom left of login screen~
June 23 2017

Version #
7.2.5.24430 ~Size and locations are same as 7.2.5.24367~

For 32-bit:
Download

Patched:

Size: 14,771 KB

~This info is for hex editing the exe yourself via a hex editer~

Force 32-bit Client A:
at offset 0009 AF1A replace E8 24 D9 0E 00 with
90 90 90 90 90

Force 32-bit Client B:
at offset 0009 AF21 replace 74 with
75

Custom Data Edit A:
at offset 000A 445A replace 84 with
85

Custom Data Edit B:
at offset 000A 459B replace 74 64 with
90 90

For 64-bit:

Patched:

Size: 24,287 KB

~This info is for hex editing the exe yourself via a hex editer~

Custom Data Edit A:
at offset 000B 8F86 replace 01 0F 84 with
00 0F 85

Custom Data Edit B:
at offset 000B 9165 replace 01 0F 84 with
00 0F 85

[jh16]

Version Release Date:
June 29 2017

Version Compiled Date: ~displayed at the bottom left of login screen~
June 27 2017

Version #
7.2.5.24461

For 32-bit:
Download

Patched:

Size: 14,774 KB

~This info is for hex editing the exe yourself via a hex editer~

Force 32-bit Client A:
at offset 0009 ADAA replace E8 DF DE 0E 00 with
90 90 90 90 90

Force 32-bit Client B:
at offset 0009 ADB1 replace 74 with
75

Custom Data Edit A:
at offset 000A 4328 replace 84 with
85

Custom Data Edit B:
at offset 000A 4469 replace 74 64 with
90 90

For 64-bit:

Patched:

Size: 24,292 KB

~This info is for hex editing the exe yourself via a hex editer~

Custom Data Edit A:
at offset 000B 8F16 replace 01 0F 84 with
00 0F 85

Custom Data Edit B:
at offset 000B 90F5 replace 01 0F 84 with
00 0F 85

[jh16]

Version Release Date:
August 3 2017

Version Compiled Date: ~displayed at the bottom left of login screen~
August 2 2017

Version #
7.2.5.24742

For 32-bit:
Download

Patched:

Size: 14,774 KB

~This info is for hex editing the exe yourself via a hex editer~

Force 32-bit Client A:
at offset 0009 AE97 replace E8 29 D7 0E 00 with
90 90 90 90 90

Force 32-bit Client B:
at offset 0009 AE9E replace 74 with
75

Custom Data Edit A:
at offset 000A 44CA replace 84 with
85

Custom Data Edit B:
at offset 000A 460B replace 74 64 with
90 90

For 64-bit:

Patched:

Size: 24,292 KB

~This info is for hex editing the exe yourself via a hex editer~

Custom Data Edit A:
at offset 000B 90C6 replace 01 0F 84 with
00 0F 85

Custom Data Edit B:
at offset 000B 92A5 replace 01 0F 84 with
00 0F 85

[Allureana]

Whew! 7.3.0(24920) changed a bunch of stuff. I can't find any of the usual data strings I used to use to locate the correct 01 0f 84. Guess I'll be waiting for jh16 to puzzle this one out. I never did understand what I was changing, anyhow. I only used to search for the strings that preceded the 01 0f 84 in the original versions where jh16 had given us specific addresses to modify.

[lululalaland]

Whew! 7.3.0(24920) changed a bunch of stuff. I can't find any of the usual data strings I used to use to locate the correct 01 0f 84. Guess I'll be waiting for jh16 to puzzle this one out. I never did understand what I was changing, anyhow. I only used to search for the strings that preceded the 01 0f 84 in the original versions where jh16 had given us specific addresses to modify.

ya i will be waiting for jh as well mate

[lululalaland]

jh can we help you somehow ?

edit:
i guess it must be pretty serious ... oh boi i just hope someone manages to remove the protection of the .exe so that i can use my mods...
I cant play legion with these shitty animations

[jh16]

Here's an update:

Due to Blizzard throwing us a curve ball on their new protection on the exe, the old ways of finding the proper locations to edit are gone. Disassembler programs return garbage code due to this new protection. Until someone can properly decipher this protection, applying edits is on hold.

[lululalaland]

oh no... no god pls no... i feared that it was because of the new protection thing... same goes for tmorph ...
god dammit...
I have no words for this.
I cant play like that. And if the possibility is gone with changing the damn dbFiles, then i cant change the spell animations and whatever the hell. Oh boi... why blizzard ?? They just have to ruin everything for me ...

[Allureana]

Here's an update:

Due to Blizzard throwing us a curve ball on their new protection on the exe, the old ways of finding the proper locations to edit are gone. Disassembler programs return garbage code due to this new protection. Until someone can properly decipher this protection, applying edits is on hold.

Every program can eventually be deciphered reverse engineered, hacked, given enough time and effort. I'd like to thank and encourage those who will eventually succeed, because it will happen. Too many people want it to happen and nothing teases a programmer more than something that says "you can't break me". All walls eventually fall. Has anyone ever read the actual encryption method used for DeCSS? Nasty stuff but it, too, fell. Anti-disassembler protections? Someone will eventually rig a sandbox and cpu emulator and run the whole affair inside that and see the innards of what's going on, or they'll just get lucky and find the tricks where Blizzard makes blocks of "data" in their code act like executable code, or vice versa. Someone will have an epiphany at 3 in the morning as the code blocks crumble to their efforts. After all, it's really just another dungeon and a meaner boss - they all go down eventually.

It might be something as simple as a tiny bit of code that reads a large block of data into memory while XORing the bits and then jumps to the new, now-executable code. Finding it may be a needle in a haystack, but if enough people jump in with bare feet, it will be found.

[lululalaland]

Every program can eventually be deciphered reverse engineered, hacked, given enough time and effort. I'd like to thank and encourage those who will eventually succeed, because it will happen. Too many people want it to happen and nothing teases a programmer more than something that says "you can't break me". All walls eventually fall. Has anyone ever read the actual encryption method used for DeCSS? Nasty stuff but it, too, fell. Anti-disassembler protections? Someone will eventually rig a sandbox and cpu emulator and run the whole affair inside that and see the innards of what's going on, or they'll just get lucky and find the tricks where Blizzard makes blocks of "data" in their code act like executable code, or vice versa. Someone will have an epiphany at 3 in the morning as the code blocks crumble to their efforts. After all, it's really just another dungeon and a meaner boss - they all go down eventually.

It might be something as simple as a tiny bit of code that reads a large block of data into memory while XORing the bits and then jumps to the new, now-executable code. Finding it may be a needle in a haystack, but if enough people jump in with bare feet, it will be found.

Lets hope that you are right. And that there are people actually looking for a solution to bypass this.

[Allureana]

Suggestion for possibly useful tool to counter the obfuscation? https://www.blackhat.com/presentatio...s-04-eagle.pdf

[jh16]

Interesting, I'll have to take a look more into this.

[lululalaland]

i dont want to pressure you or anyone ... but can you give us an update on our current "situation" ?
No matter the outcome, id still like to thank jh for all you have done for us in the past years and im really grateful for your work so far. I cant express how much i owe you because of the wow.exe that you provided in wod actually got me into wow modding. So yeah...thx mate. Thanks a lot.