Originally Posted by tardmrr
In WoW's Lua, loadstring's ability to load bytecode is deliberately disabled. What you see there is not bytecode. What they've done is put the entire addon into a string and then encrypted it. I didn't bother to look at the specifics of it, but if you really care, you can always hook loadstring and watch what gets passed to it.
|
Okay I guess the fact WoW cannot load bytecode directly is reassuring somehow, thanks for pointing that out. You can blame me as I actually did not check the code at all when I first saw the mess (although the first copyright line being cleartext was bothering me) but you are right, this is nothing else than a loadstring... A huge ugly string with a lot of \' escaping
I personally dislike such tricks quite a lot but that is another story
But then again you can intercept the decrypted script before it is compiled into bytecode and passed on to the interpreter right? So I guess my question to the admin remains. Do you guys know what is in there?