I find this thread hysterical.
I've been a systems administrator for IBM and then Dell for about 8 years total now, and when a distributor tells us "this isn't supported", both of my companies have had no trouble understanding the concept of "well if we do this and something goes wrong they aren't liable in any way since they clearly stated what we're trying to do is unsupported".
When you buy a computer from any company out there, ANY AT ALL, and they designed the system to be "optimized" for Windows 7, and then 4 years later Windows 8 comes out but they dont release drivers for it, thats called UNSUPPORTED.
Same concept here people. All Bashiok and Blizzard are saying is "We told you not to do this and we told you we dont support it, so when something goes wrong with it you're on your own."
Following VERY SIMPLE DIRECTIONS is hard.
Everyone keeps pulling up the technical aspects of this when its a simple yes or no answer. The answer is no, Linux does not have D3 support, meaning if you chose to run it on that OS you get no support when things go wrong. If something WINE or something else running while D3 was being emulated triggered Warden, that's not Blizzards fault. You were still doing something unsupported in the first place.
I couldn't agree with you more. I have been in IT for 14 years, doing lots of System Administrator work. Now I work in professional services. When things aren't supported out of the box for a product I get paid (I'm not cheap either, custom dev is billed at $250/hour) to take all your back end server tools and make work flows so they all work together.
Furthermore, I specifically work in the Linux and Mac field. I really don't touch Windows boxes at all, but I do touch Active Directory when doing LDAP integration and single sign on stuff. I can tell you no technology is 100%. No technology is fail proof. Everything is imperfect and has a rate of failure. If it didn't I would not have my job.
That being stated, there isn't a lot of info on how Warden works. It apparently creates hash files of apps running in the background of your OS and then compares them server side to known exploit and cheat apps. I can tell you right now, this method has a margin of error. It also claims to leverage Operating System APIs. WINE itself is an API that runs windows apps in their own self contained environment (they call it a wine bottle, clever I know..) so when battlenet is launched from an app in WINE it should be running in it's own environment. The tricky part is, the app itself is being fooled it is running in Windows, and I high doubt Warden is tested for every build of WINE, nor should it be, since after all, it is not supported.
I think the bottom line lies here:
1 - they cheated (however I haven't seen any evidence proving so)
2- Warden is bugged
I am going to lean towards 2 until someone can confirm with out a doubt they cheated.TL;DR = Software is always buggy, that is why there are these things called patches and hot fixes