- #Warcraft 2 map editor disable buildings list plus#
- #Warcraft 2 map editor disable buildings list free#
Fans of World of Warcraft will undoubtedly feel at home as ECW '0. Extreme Candy War 2.īlizzard's Halloween map where Alliance and Horde fight it out on the battlefield. Since Warden reads from "B" + offset, when it reads from our fixed base address "0x401000" + offset, it will read the same area in memory (and would match the same hash).Warcraft III - Maps - Bonus Maps. Disabling ASLR makes our World of Warcraft base equal to 0x401000 each time. This is why when a packet to check the hash of an arbitrary address "0041F312" is sent, it would have to read from the "base" to get the relative address OR it wouldn't be the same each time. So, WoW must implement some feature of reading from "B" + offset (relatively) to get the hash of the data. Therefore each time Warden checked "0041F312" in memory, it wouldn't match the hash "X" and everyone would be banned. Since everything is shifted due to ASLR, "0041F312" (directly in memory) won't be the same contents. Right? Then my hash "X" will match (if nothing is modified). So, regardless of each World of Warcraft instance I start, the data in that instance's address "0041F312" must always be the same. By your logic (which is incorrect), "0041F312" in memory must always have the same data. Since WoW is ASLR, your base address will be some variable "B" (it changes each time that's the point of ASLR) Blizzard servers tell Warden to check a HARD CODED ADDRESS "0041F312" in memory to match a hash "X". I am assuming this is what you think (or thought):
"0041F312", on each instance, of World of Warcraft will not be the same (UNLESS World of Warcraft has a fixed base - ASLR is off). That offset is valid for both bases?It must be base + offset to get the hash of the address. The server sends a warden check, address 0041F312.
#Warcraft 2 map editor disable buildings list plus#
Plus you are filling my thread with utter nonsense (other people MAY actually believe what you said, which is incorrect).ītw, I do explain the reason for disabling it on my main post. You are assuming stuff that doesn't make sense. I just dislike it when people, like you Lecht, try to talk about something they don't understand fully. I am well aware of all the features Warden currently has (much thanks to Cypher for his blogs & talks on MSN) in its arsenal. Before playing around with ASLR, I made sure that I understood what it did (and why it was implemented). I'm not trying to say I'm "smart" (or know everything) regarding this stuff (in fact, I'm a newbie in reverse engineering), but at least I don't "pretend" to know it. This is a problem with a lot of people on the forums, not just you. Lecht, you should understand the concepts here before you talk.
#Warcraft 2 map editor disable buildings list free#
You really need to read what ASLR is: Address space layout randomization - Wikipedia, the free encyclopedia and what it isn't.
So, if Warden does do a "checksum" of an address in memory (base + offset), it will STILL RETURN THE SAME VALID VALUE. Why does this have anything to do with a checksum? Disabling ASLR doesn't ALTER any of the "contents" in memory within the program. If it returns false, your banned =).No, you BOTH obviously don't understand. I can verify what Lecht says, If warden does a consitency check like it does for many other files and addresses.