[Gambas-user] How to protect gambas code from reverse engeeniering?

[Jussi Lahtinen]

... also all that is probably a bad idea. Why do you need this? For DRM
(there are better options)? To protect game story?

Jussi

On Sat, Mar 25, 2023 at 6:46 PM Jussi Lahtinen <jussi.lahtinen at gmail.com>
wrote:

> I am developing software and create the .deb package for installation.
>>> What I wish is that noone can easely reverse the code I am doing.
>>> Yes I know that at least, it is possible to  read the final assembly and
>>> reverse it,
>>> but i just want to to make that job more difficult to attackers.
>>> In other words, is possible to have a compiled version of my gambas
>>> software
>>> at the same way i get executable code form my C source with "gcc code.c"?
>>>
>>
>> I don't quite understand your question. You can compile Gambas into
>> bytecode executable and leave the source code to yourself.
>> You need something more than that?
>>
>
> I'll just add that it is very easy to disassemble compiled C code (IE
> executable) back into C code, because of the available tools.
> However, converting Gambas bytecode into Gambas source is tedious, because
> AFAIK there aren't ready tools for it.
> If you need something more, you need to do source level obfuscation.
>
> Jussi
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gambas-basic.org/pipermail/user/attachments/20230325/67450f70/attachment.htm>