*This text is part of the project javaencrypt. Currently is stopped because a change of ideology about free source code and learning issue.
Obfuscating with dirty code
One of the easiest and more dangerous ways of obfuscate a source code is adding dirty code.
This means adding lines of functions and variables with no objetive but the interruption of the original code interpretation.In the proccess of writing an useless code, which is very simple at first, we may be careful with what we write and where we do it.
We must know that the more simbiotic a dirty code is with the original one, more obfuscate effect will have, bearing in mind that the final result never will so optimize as at first
and the more tedious code lines we insert, the more slower and heavier the program will be.Writing a dirty code may be a very simple task, we just have to add variables and functions to the original one what will interact
with them without touching the real code.
However, this involves a very poor obfuscation since with some of reverse engineering we may get real lines and
throw away those which are just filling in.
A good dirty code may interact with the real code and be next to it like a vital part itself; the final code must integrate the dirty code so well that no even itself could work properly if we trip all the added signs.
but the possibility of writing functions and modulus as well as define variables in any part of the code, may give us an advantage
when set up the obfuscate code. With these characteristics we can define bucles for and while with any original variable and play with themselves in and out the functions.Sequential code :
Adding dirty code:
In the code-mixing proccess we must always find the harmony between obfuscation, fluency and optimization of the program.
of the CPU slowing the navegators and the computer, which means that all the work made for obfuscate it, won’t be useful.