Custom code injection : Let users create their own code(dll, exe) and put it inside your map, making code auto-executed as their map run.

Custom code execution can enable everything you've imagined in SC. You can even recreate Leauge of Legend in SC. Everything is possible.
But Custom code execution may compromise security severely. You can also create virus in SC. Everything is possible.

So, should research for custom code execution be continued?

Post has been edited 2 time(s), last time on Jul 1 2014, 12:56 am by trgk. Reason: Clarification.

If another security breach is created then it will be patched out relatively soon, Blizzard has the source code but will never use it to add something to sc1, only to protect their dignity by keeping the game barely functional.

Would this require a different SCBW executable? I don't understand SCBW's normal map process, so I'm just unsure as to how you can actual inject code that will be executed into a map.

Abusing overflows, how else? http://www.staredit.net/topic/16427/ note that my exe launching outline lacks many non-zero'd values that need to be worked backwards from, and an example map which I've neglected to complete.

As for my part i'll press forward with discoveries and trust mapmakers; no one abused EUDA's before they were patched to make a virus AFAIK, and it was 400x less work back then to launch executable code.

Do it for science!

Blizzard will just have to patch the game.

So what are you afraid of?

"Now I am become Death, the destroyer of worlds."

At this point I think they'll rather just close down bnet for sc1 and declare it dead.

And opensource the game as consolation

My opinion :
1. People can't avoid downloading executable code if there is one in the map they're playing.
2. We cannot revert exploit disclosure once it is disclosed.
(It have already been disclosed in rather very cryptic manner. I understand it though with some difficulties)
3. Exploits shouldn't be disclosed until they are fixed to prevent possible abuses.
But Blizzard won't fix SC. (I would be very happy if they would) Therefore shouldn't disclose the method for it.
4. People may do research, but they shouldn't distribute "How to put your own DLL inside your map in 10 minutes" manual things.

cf) Blizzard patching SC1 again? 1.16.2? They dropped SC1 support several years before. I think that's just a false hypothesis;

Make a map that has an EUDA enabler, injecting the needed bits into the players' StarCraft, then you can stop research.

Alright, my ears just officially perked up

this