QUOTE(T.s.u.k.a.s.a @ Aug 12 2005, 05:19 PM)
...since EUDs didn't pose a threat. Besides, if I had mad programming skills I might even be able to execute a small virues with a play wav trigger and a dupe map that constantly shows the text "Preparing Map. Please Wait...", no help from EUDs.
[right][snapback]286555[/snapback][/right]
Ok, now first of all... who are you to say that EUD triggers didn't pose a threat? Are you an expert at code injection? Not only did a more knowlegeable person say that there are methods to doing it (with EUD triggers), but regular triggers pose no immediate threat if more buffer overflows aren't found.
Let me get this straight, you're saying that if you had knowledge in programming, you'd somehow find a buffer overflow in the .wav playback code and manage to execute code? How do you know that such an exploit exists? Or was it just pure speculation that a large portion of SC trigger execution/wav playback code was insecure and contained a crapload of exploits?
Back to my point: go ahead, try to find another buffer overflow that could be exploited by SC maps to prove that EUD's weren't a significant problem in comparison. Or, prove to me that EUD's didn't pose a threat at all. Just because no virus maps popped up yet doesn't mean that it's not possible.
Blizzard's goal was to make SC as safe as possible, and leaving a hole in that they know about which could be used to execute malicious code wasn't part of the plan. If a virus map was ever made, they'd get a ton of complaints from the non-map making crowd. You can't compromise the safety of the whole user base just so that a portion could have freedom to do whatever the hell they wanted while making a map.