[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Proprietary lua code
- From: Jon Chesterfield <jonathanchesterfield@...>
- Date: Sun, 28 Jul 2019 12:15:12 +0100
---------- Forwarded message ----------
From: Srinivas Murthy <email@example.com>
To: Lua mailing list <firstname.lastname@example.org>
This topic might have been discussed before.
We have proprietary lua code (along with C/C++ binaries) made available as a self-downloadable package (by our customers) and we need to keep it hidden for various reasons (security, IP protection, etc.).
What is the recommended mechanism in lua for this?
Can you expand on the requirements? For example, how do you meet them for the C/C++ binaries?
If the C is shipped as x86-64 in elf or coff, then shipping lua bytecode in a section is equivalent. If the x86-64 is decrypted on the fly then the same method can apply to the lua.
Similarly, how do you defend against running the compiled C under debuggers? There may be similar countermeasures that could be built into the running lua interpreter.