Re: obfuscating / protecting LUA code

[David Given <dg@...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Kein-Hong Man wrote:
[...]
> Once someone finds the main VM function using a debugger, the game of
> hide-and-seek is essentially over. If the Intellectual Property is
> really, really valuable, legal action is probably the only way to stop
> commercial duplication of your work. Reverse engineering is hard to
> stop. What method you choose depends very much on the "whole picture".

*nods*

After all, the *computer* has to figure out what the code does in order to
execute it; this means that a human can, too. The best you can do is to make
this hard. You can't make it impossible. Make things *too* hard and you end up
shooting yourself in the foot, because you'll end up making your life a misery
for yourself.

I'd suggest that probably the best thing to do is to compile the bytecode with
luac (so there isn't obvious source code lying around), and then put a licence
on the finished product saying that your users aren't allowed to copy it.

- --
+- David Given --McQ-+ "If you're up against someone more intelligent
|  dg@cowlark.com    | than you are, do something insane and let him think
| (dg@tao-group.com) | himself to death." --- Pyanfar Chanur
+- www.cowlark.com --+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEUlmQf9E0noFvlzgRArRIAKDeI9TBhxNrRhNBpkoSPqOMbS7KHwCfe+Mi
0xBurM6MU9M1DTc9Ra86AjM=
=DDRf
-----END PGP SIGNATURE-----