4.0.x does md5 hash checks on files...

[zamboo]

So it appears now WoW checks all files md5 hash and if any small data is changed "4 changed to 5" it will not allow the game to run...I'm trying to do some login screen edits and play with the LUA's for the login screen and if I change anything it will say corrupt and not load...

If anyone figures out a way to do this let me know, i'll keep playing with it.

[Herbalism]

Do you have a GlueXML free WoW? I can't think of anything else.

[schlumpf]

GlueXML and FrameXML have always been protected.

[Herbalism]

They are removeable though. I happen to use a GlueXML free one.

[zamboo]

Really? How? Yeah it's GlueXML and even a change of a single byte makes it stop working. What do you mean glueXML free wow? This is on the new 4.0.3a patch on PTR. How did you bypass this protection? I also see md5 hash *.lst* file in MPQs now...

[schlumpf]

That MD5 hash is not used for GlueXML protection. There is a .toc.sig file for that.
You can easily remove the checks in the client. The problem there is, that you will have problems with Blizzard's check for the client's checksum upon logging in.
Solution: An injection patching that check, then upon checksumming removing the patch and afterwards restoring it.