Re: obfuscating / protecting LUA code

[David Given <dg@...>]

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

Shmuel Zeigerman wrote:
[...]
> There's one point that seems to be not mentioned yet - obfuscating names
> of variables. It's not easy to understand non-trivial code as it is, but
> if all the variables look like a137, d86, etc., the cracker's task
> should be much harder to accomplish.

If you use locals everywhere you can, rather than global variables (a good
idea anyway because it'll speed things up), then the compiler doesn't keep
track of the names therefore they won't get emitted. (Except in the debugging
code, with you remove with the luac -s option.)

Global variables are, after all, just syntactic sugar for accessing the _G table.

*Don't* obfuscate your source code unless you truly desire a long stay at
Arkham Asylum!

- --
+- 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

iD8DBQFEUoYLf9E0noFvlzgRAuVbAJ4gTJcdZoN/r78ZsItb9hacG4QUwQCffZXx
vQb2qs6YtD8KpgRWqtbtNxQ=
=0799
-----END PGP SIGNATURE-----