In his latest column, the pretend computer security “expert” John Eldridge again raises FUD (Fear, Uncertainty and Doubt) around Warden, regurgitating the following urban legend:
“It (Warden) reads the text in the title bar of every window you have open including that really embarrassing Furry fan site you don’t want your friends to know about. Yes Nekudotayim, Bliz knows about your pr0nz.!“
Yet in the following sentence, John contradicts himself (and actually gives a technically correct information):
“The Warden then creates a hash code (think fingerprint) of each window title and compares the results to a list of ‘banning hashes’ for potential matches and subsequent divine retribution.”
The rest of the post is full of the same ambivalence, alternating between factually correct information and fearmongering (comparing Warden to Spyware, insisting Blizzard knows about your browsing habits).
The key distinction John fails to make, though, is that while Warden “knows” without recognizing or understanding what is happening on your box, Blizzard doesn’t.
What exactly is a hash code? It’s quite simple. You take a word or sentence (for instance in the present case a browser window title), apply a non-reversible mathematical function (the same kind of operations used in modern encryption) and you get a relatively short alphanumerical code back – your hash code. As mentioned, the function is not reversible, in other words, from a given hash code, you cannot deduce the original word or sentence.
Blizzard takes a certain number of known cheat programs and sites and runs them through their hashing function. This gives them a dictionary of sorts, a list of suspect hash codes. Every 15 seconds, Warden hashes every running process name, the names of open windows and browser pages, and compares each hash code to that dictionary (or sends it back to Blizzard and the comparison is made there, it isn’t entirely clear where the action takes place). If any of those Warden-generated hash codes match what is on the dictionary, Blizzard’s processes against cheating will be set into motion. The rest of the hash code generated from your box is totally useless. There’s no way that Blizzard will be able to determine (and will even want to determine in the first place) that a specific code hashed by Warden on your computer is actually you looking at www.steamingtaurenaction.cw
Again, let me stress that point: Blizzard cannot identify any application, process or data gathered on your box which doesn’t match its list of potential cheating software.
Beyond that, my point made when patch 2.3 was launched still stands:
“As all the other reasonable commentators keep pointing out, if you do not trust Blizzard with your privacy, there’s only one solution, uninstall the game and quit now. What Warden does is totally irrelevant in that context, and focusing your ire on it at the exclusion of the rest of WoW basically just shows that what you’re really after is posturing on message boards.
Plus, face it, it’s not as if your private data was interesting anyway. Nobody cares about your secret pr0n stash on your home computer, least of all Blizzard. If it’s professional data, even simpler, you shouldn’t play WoW on a work computer no matter how lax your employer might be about that. The only thing Blizzard may want is your credit card number, and chances are, you gave it to them already.”
Face it, unless you’re cheating, your private information is not interesting to Blizzard (and anyone else). You’re not a special snowflake. Your draenei tentacle pr0n stash is boring. Your domestic accounting spreadsheet doesn’t matter to anyone but yourself. You disclose more information about yourself and your habits whenever you pay for your food with a credit or debit card.
WoWInsider has a long standing and bad habit to stir up controversy and fan flames in lieu of relevant discussion, starting at the very top with Mike Shramm himself. Computer security is, however, a grave enough subject that playing the same game of bait-and-switch hack posting representative of the worst the site has to offer is irresponsible and foolhardy. If you term yourself a computer security expert, feeding paranoia on false representation for the sake of generating comments and traffic is something which your work ethic should forbid you to do, at all costs.



I read the article in full, and the conclusion I came to was that unless Blizzard was being hired by big brother then they would have no reason and not enough means to sort through and categorize all the viewing habits of wow gamers, and while invaluable to marketers this information would be useless otherwise. If big brother wanted to watch me – well he is quite welcome to read my blog – thanks for putting up another side of the story..
Good work!
FUD needs dispelling.
Very nice article. I’m with you 100%, if you’re worried about being spied on by Blizz, uninstall WoW and every other Blizzard product on your machine. Don’t expect to have any REAL FUN in the future, though!
The guy who wrote that article is not very knowledgable about Warden. But no offense, niether are you. Unforunately, the most knowledageable people (the ones hacking it) are also viewed as the least trustworthy source. It’s a catch-22.
Anyway… I suggest you educate yourself by reading this post:
http://onwarden.blogspot.com/2007/11/storm-is-brewing.html
And then my own thoughts about Warden and Privacy.
http://serialganker.blogspot.com/2008/03/privacy-versus-protection-of-digital.html
Ultimately, your 2.3 quote is accurate but it does require a lot of blind faith in Blizzard. It’s a blatant abuse of privacy that people (including me) willingly accept to play their game. The central issue is not whether they do it or not, but that there is no TRANSPERANCY into WHAT they are doing.
I’m fully aware of what the onwarden blog talks about, in fact, it was one of the different things which triggered my November post. And it actually doesn’t demonstrate that the inner workings of Warden have suddenly changed.
I stand by all my points. If you have data which you believe to be at risk from Blizzard, don’t play on the same box, or play on a virtual machine, or a wine instance over a Linux distro. You don’t get to reverse-engineer the patches either.
That being said, discussing cheat protection methods and user privacy is a fully legitimate topic. Preferably disconnected from sensationalism about what Warden could possibly do if Blizzard were suddenly willing to get a hold of your steamy draenei pr0n.
You wouldn’t know if the inner workings of Warden did change. They made sure of that back in November. That’s what I mean by transparency. It’s all blind faith that Blizzard isn’t looking at your draenei porn. And while it’s all well and good to have faith in Blizzard, I have less faith in a disguntled Blizzard employee with a vindictive streak. Such an employee may not exist, but they COULD exist and COULD be inflicting harm and you would be none the wiser. It’s an interesting situation where WoW users willingly allow the program unfettered access to your entire computer.
(For accuracy, I suppose you would know if Warden changed, just not how it changed.)
How is that any different with Windows Update for instance? The same concerns extend to nearly any piece of software. They aren’t even new or tied to our current online life – Unix co-creator Ken Thompson once designed a version of an early C compiler which wouldn’t just add a backdoor to software it compiled, but include the backdoor adding code back into any recompilation of itself.
Truth of the matter, the only way out of this lies with open source. Seeing as neither WoW nor the OSes most of us are running it on are open source, the whole argment is a bit of a strawman.