Anti-Decompiler [Download]
#61
Posted 12 April 2009 - 09:36 PM
lol
i will probably use it if i ever make a game
i dont use instant play anyway
#62
Posted 18 April 2009 - 08:28 PM
To the first question, no. There is no way to absolutely stop hackers. It may stop the current decompiler, and although Clam (creator of the decompiler) does not want to override this application, there is always the chance someone else will.
And to the second question, yes.
-Ampersand
#63
Posted 18 April 2009 - 08:53 PM
This is not the case, (usually). Clam created the decompiler to help people who lost their source...
#64
Posted 24 April 2009 - 02:39 AM
#65
Posted 30 April 2009 - 11:35 AM
Thankyou, too, for developing this =)
#66
Posted 30 April 2009 - 02:17 PM
#67
Posted 30 April 2009 - 08:09 PM
Another made up "fact" on the GMC...[...]Clam created the decompiler to help people who lost their source...
He claims he made it because he was making a point about GMK encryption, and how it's only lead to the documentation of the encryption and file format, which eventually lead to testing on exes, which lead to the decompiler. He never mentions doing it to help people who lost their source. My source is the about statement of said program.
#68
Posted 02 May 2009 - 09:08 PM
Edited by makerofthegames, 02 May 2009 - 09:09 PM.
#69
Posted 03 May 2009 - 12:05 AM
Another made up "fact" on the GMC...[...]Clam created the decompiler to help people who lost their source...
He claims he made it because he was making a point about GMK encryption, and how it's only lead to the documentation of the encryption and file format, which eventually lead to testing on exes, which lead to the decompiler. He never mentions doing it to help people who lost their source. My source is the about statement of said program.
It isn't a made up fact. It's real. Clam is a good person...
Enough of this, the anti-decompiler doesn't make it UNdecompiler. You just need a custom one...
#70
Posted 03 May 2009 - 12:34 AM
Another made up "fact" on the GMC...[...]Clam created the decompiler to help people who lost their source...
He claims he made it because he was making a point about GMK encryption, and how it's only lead to the documentation of the encryption and file format, which eventually lead to testing on exes, which lead to the decompiler. He never mentions doing it to help people who lost their source. My source is the about statement of said program.
TBH, I made it just for the sake of seeing if it would work. It occurred to me afterwards that it was ironic that encrypted gmks had led to its creation. It was leaked, I didn't want people thinking they were clever for having a copy, so I released it along with that jab at YYG. If I can ever be bothered I'll cleanup the source and release that too.
#71
Posted 03 May 2009 - 12:39 AM
Oh. Well, thats the explaination.
#72
Posted 03 May 2009 - 10:36 AM
Actually, the decompiler is using obfuscated self-modifying bytecode, and is literally impossible to decompile unless you do it by hand, which will take a very long time and a lot of skill.<off topic> You can just decompile it...(java is bytecode...)</off topic>
Edited by score_under, 03 May 2009 - 10:37 AM.
#73
Posted 03 May 2009 - 02:21 PM
However, I have noticed that when you decompile Java, it doesn't restore the original variable names...
Kinda like the near impossible conversion from assembly->C
Edited by PickleMan, 03 May 2009 - 02:24 PM.
#74
Posted 03 May 2009 - 03:09 PM
Of course not; the only reason this works in Game Maker is because the scripts aren't compiled, and the only time this works in C is when you export it from a dll.However, I have noticed that when you decompile Java, it doesn't restore the original variable names...
Most non-compiled languages don't reference a variable by name, rather by an identifying number. Most compiled languages reference variables by their own unique pointer. (Most of the time, a constant pointer means a global variable, while a pointer relative to EBP or ESP means a local variable.)
Near impossible, but with a little practice, it's possible to do it manually. This is how "execs.dll" actually came about.Kinda like the near impossible conversion from assembly->C
And it's what I do for fun
#75
Posted 03 May 2009 - 03:17 PM
variables are just places in memory...
#76
Posted 05 May 2009 - 04:50 PM
#77
Posted 05 May 2009 - 05:07 PM
#78
Posted 05 May 2009 - 05:24 PM
No, it just detects the packer; it evidently doesn't have any code to unpack the detected packer (most likely FSG) so can't see the original code to scan it for viruses.Bahh.. My antivirus says this is a packed virus.
#79
Posted 05 May 2009 - 05:39 PM
#80
Posted 05 May 2009 - 11:50 PM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users









