Re: Who is using modified Lua versions, what are they and why?

Cool, thanks! I'll give it a read!

And yes, indeed, it's not necessary to modify the Lua interpreter/compiler
for that. But a bigger goal was to obfuscate compiled bytecode even further.

Again, on the compiler level, messing up with OpCodes, etc. But the project
did not come to that in the end.

Kind regards

On Tue, Jul 7, 2026 at 3:11 PM Lourival Vieira Neto <[email protected]>
wrote:

> On Tue, Jul 7, 2026 at 8:51 AM Ką Mykolas <[email protected]> wrote:
> >
> > Some time ago I've been developing an encryption and signing tool for
> compiled Lua chunks.
> >
> > It involved a few slight changes in luac and lua:
> >  - swapping calls to "require" with different call to a different
> function with statically determined parameters during compile time
> >  - updating "lua_load()" (?, or some other loader related functions)
> with signature checks and loading from encrypted binary blob
>
> interesting; we have developed a support like this for Lunatik without
> modifying Lua [1, 2, 3, 4].
>
> [1] https://luainkernel.github.io/lunatik/modules/darken.html
> [2] https://luainkernel.github.io/lunatik/modules/lighten.html
> [3] https://github.com/luainkernel/lunatik/blob/master/lib/luadarken.c
> [4] https://github.com/luainkernel/lunatik/blob/master/lib/lighten.lua
>
> Regards,
> --
> Lourival Vieira Neto
>
> --
> You received this message because you are subscribed to the Google Groups
> "lua-l" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion visit
> https://groups.google.com/d/msgid/lua-l/CALHoKCZ8FMgoxx0%2B-ghW1i4Lu49Ei-1UN6sG79-Kf%3DnG_aYEiQ%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups "lua-l" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion visit https://groups.google.com/d/msgid/lua-l/CAFs3%3DcK1J5knUFr2D_Rzx4qUcYaFNaFp-pZoqfqFBXfeCw24yA%40mail.gmail.com.