Slashdot Mirror
Linux Users Banned From World of Warcraft?
Turmoyl writes "Many Cedega (formerly WINEX) users claim to have been mistakenly caught up in a security sweep of the U.S. game servers performed by Blizzard's World of Warcraft Game Master (GM) staff. Affected users received the same strongly-worded 'Notice of Account Closure' email messages that true bot users did, in which they were accused of the 'Use of Third Party Automation Software.' While diagnosis of this event continues early speculation points to Blizzard's use of the Warden anti-cheating spyware application that is bundled with World of Warcraft, and the odd things that may have been produced by it when it was run via Cedega. Emails to World of Warcraft's Account Administration staff continue to go unanswered while the list of affected people continues to grow."
Well, I've talked with someone who does a lot of this sort of stuff and he explained to me that long ago when Blizzard first debuted WoW, it was an instant success. And there were many people that had developed scripts (duping, afk farming, etc) for games like Diablo that wanted to to do the same thing for WoW.
... after all, you don't want a GM messaging your bot as he sits idle doing his repetitive task, do you?
The art of doing this successfully lies in knowing what addresses of memory that your client application is using to store data. You change these memory addresses & your client's state is altered. But there's some things you can't change because they're located on the server. Realistically, the client has to do some of the computation and storing itself (and with WoW being some huge multi-gigabyte client, there's a lot to investigate). Obvious, you want to reduce network traffic and give your servers a break so you design this to have minimal communication.
The problem then becomes that users will write applications to modify the data & memory that their client applications are using. What results is signals sent back to the server which aren't true and give that user an advantage. Solution? Enter Warden to check these memory spaces and files for any potentially unauthorized changes (checksums, whatever method they want to use or seeing which threads are accessing that memory). And how do you protect Warden from it itself being hacked? You design it kind of like a root kit--that is the user shouldn't be able to alter or disable Warden & they lose the domain over that tiny bit of functionality of their hard drive.
My guess is that before, they were checking if there were any known scripting or programs that were unauthorized and changing this data. And they were banning those and only those accounts. I fear that it now does a verification on the memory space, files & system registry to ensure that it is not being molested by another application or tweaked at all. I am guessing that they have changed the ban notice to ban whenever this verification stage fails and that Cedegra does not emulate Windows to the point of their verification satisfaction or to the point of Warden being able to query all other running applications. Worse yet, I fear they may look to integrate this with the WGA with Windows & some other means with Macs--though that is pure speculation on my part.
The irony of it all? The fact that a talented programmer with burp or some other styled network tool and use linux on a routing box to intercept packets and change them to give him position hacks. Unfortunately, if you use this too much, I believe that random server side verification checks will eventually catch up with you but I can't say I've ever implemented this or been caught using it.
Which brings me to one last point I'd like to make on this topic. I think that this cat n' mouse game of Blizzard versus the cheaters is good for AI. The last possible domain we have is people writing applications that extract data from video memory and use computer vision algorithms to write if-then-case bots. Yes, bots are bad but this is driving people to a corner where they essentially strive to pass the Turing Test
My work here is dung.
Windows users got banned. Linux users got banned. Not all Windows users got banned. Not all Linux users got banned. Could it be that the banned Linux users where doing somthing byond just using Linux?
Naw, cant be.
"Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
There is a long history of folks blaming wine for bannings in WoW, and I would wait to see exactly what happened here, before assuming that Blizzard has gone off the deep-end and started attacking those users who have clearly gone to great lengths to be able to run the game.
PS: If you want to run WoW under Wine, here's what I did on my Fedora Core 5 system using an NVidia card with the binary NVidia drivers:
It now works fine. The only problems that I have are:
On the other hand the benifits are huge:
Overall, I love WoW under Linux. It's a joy compared to some made-for-linux games I've tried to run, and wine really seems to have come along.