*shrug* I am not appolgizing for Blizzard but stating things learned from years of this in WoW. The way Battle.net authentication works, the client is told who is playing not the other way around. There is no way to rig either the WoW or SC2 client to switch Player IDs while connected so I'm inclined to believe there is no way to do that in Diablo 3 as well. All objects are treated as anonymous objects commanded by the server to move so there is no connection or communication player to player. The tech just doesn't support the kind of things some posters are claiming it does.
And I am not claiming Battle.net is 100% secured either but I am going to claim that it is probably easier to hack random desktop machines and random people. Years and years and years of this where every time I've had to deal with it, it turned out to be something a player did instead of Blizzard. It isn't that any of those people were stupid or were careless but those guys are incredibly clever and persistent. WoW and Battle.net attacks are often the first time people have ever dealt with identify theft and they often they are angry and embarrassed it happened to them where the last thing you will get from them is all of the facts partially because these schemes often involve never noticing them.
Could there be something wrong with the Diablo 3 client that leaks sensitive info to a hacker? Yes there could be. Is it more likely that the player accidentally exposed their account information outside of Battle.net? More likely by magnitudes.
Log in to comment