Re: Making a partial C compiler

"John Eskie" <cyberheg@l115.langkaer.dk> writes:


> When I said flow obfuscation I really had something as this in mind:
>
> 1. Variable and function name string replacement (more of you
> already wrote how that can be done).


> 2. Introduction of parallel code i.e. dummy code which doesn't interfear
> with the real program but make things harder to read since you gotta figure
> out what is real and what isn't real.


Warning: optimizer can remove this dummy code.


> 3. Rearranging of code so if you got 3 blocks of statements A, B, C you can
> do:
>


Optimizing compiler (for example, gcc with -O1) will re-arrange these
blocks back. Do you agree to distribute slow unoptimized code?


> 4. Dynamic "linking" by making exact function calls to be resolved at
> runtime by using function pointers.


It may help, especially with name obfuscation.


--
Ivan Boldyrev

Return to the comp.compilers page.
Search the comp.compilers archives again.