I can still benefit from the fact that automatically generated code (in this case automatically converted Perl code to C code) is fairly unreadable.
It's not. It's all but trivial for anyone competent with Perl to decompile it to the original Perl code.
To translate Perl to C automatically, you have to reimplement Perl in C. No one wants to do that, so they translate the Perl source code into something that the resulting program can feed to libperl when it runs, and that's the point of vulnerability if you think you want to hide things.
In short, it's technically possible, but it's so time consuming and difficult that no one competent to do such a thing would waste the time and energy to do so.
You're more than welcome to try, but you should believe people with years and even decades of experience with Perl who tell you that this is not worth your time to pursue, because the simple approach offers laughable "protection" and the effective approach will take years of difficult work to make practical.
In reply to Re^5: Automatically Converting Perl to C
by chromatic
in thread Automatically Converting Perl to C
by blueberryboost
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |