Decompilation

OZApps

I know this is not an issue of Gideros, but Lua, the compiler luac compiles text into bytecode and the source code for luac is available for all, so in theory, it is easy to write a decompiler converting the bytecode back into instructions as the names of the variables and functions do remain. So how safe is code from this process? I do recollect Gorkem mentioning encrypting the code and the slight delay/performance lag it may cause, but would that make it any safer?

It will only be a matter of time when users will have lost all the source code and the only thing that would have survived would be the compiled app that will form the basis and case for decompilation.

atilim

Hi @OZApps,

I have done only simple tests but http://luadec51.luaforge.net/ does some good work about decompiling Lua codes. After decompilation, the names of local variables are completely lost but names of global variables remain same. Although, there are some obfuscation tools, this problem also exists for other languages like C# and Java. (btw, obfuscation tools don't protect C# and Java codes completely, they only rename the variables and classes so that reading the decompiled code is harder).

For encrypting the code, if someone is able to find the encryption algorithm and the private key, he/she can decrypt back and then decompile it. But I can say this won't be an easy process (except for experienced crackers).

cheers,

OZApps

I agree with you Atilim, even simple decompiling is not a straight forward task for the average user. However having said that, it is just about safeguarding code. An experience hacker/cracker can even decompile the compiled Assembly so what is bytecode.