Hey, i've set up a Warden Wiki page with enough information to hide yourself from warden. Feel free to add to it, add descriptions to the addresses i can't be arsed to .
Warden - WoW.Dev Wiki
Hey, i've set up a Warden Wiki page with enough information to hide yourself from warden. Feel free to add to it, add descriptions to the addresses i can't be arsed to .
Warden - WoW.Dev Wiki
Very nice. Just got home, I'll add to it in a sec.
EDIT: Added some stuff, I'll do more later.
Last edited by Cypher; 09-01-2008 at 02:05 AM.
I love that the wiki is being updated +Rep 3x for kynox (If I dont have to spread...)
Woah, nice, thanks =D
Take care of the style a bit. So many lists. .__.
Are the LUA-Strings and driver-names all it checks?
Cypher: One ? is enough. :____. I hate it, if people spam questionmarks. .___.
Kynox: Is it really "Page is based on WoW 2.4.3 01/11/08 by kynox"?
Thanks for bringing live into the wiki a bit. Feel free to add more!
You hate multiple ? and I hate anime faces o.0 .___. ;.; XD =*0$5FFEJsomethingelsedumb. Deal with it.
Edit: Now that I think about it, I also hate nitpicky twats.
Non-American dates dude, 1 september.Kynox: Is it really "Page is based on WoW 2.4.3 01/11/08 by kynox"?
your not american?
No. (filler)
I am european. Think about the */11/* again.
Oh right, i wrote it early morning, and read your post just as early. Long days ftl
Would it be possible to dynamical detour wardens crc funktions to check other memory reagions?
Then you'd just had to save the bytes warden scanns and redirect the scan to the byte array :-)
You could dynamically check what Adresses Warden scanns and redirect every single warden scann to fake bytes, you'd also need a function to calculate the size of the scann, because you need to know how many bytes to copy.
Is this a good Idea?
I hacked 127.0.0.1
well... you could restore all the bytes that warden checkes, whenever it is checking them and modify them afterwards... but i'm no expert in warden-theory don't know whether you can hook it that simply.. maybe warden is just too different every time...