J
Jacky Luk
I saw an old thread in this group which addressed the issue of reverse
compilation. After some study, I draw a conclusion that "reverse
compilation" is completely blocked off in win32 environment (except in .NET
languages like C#) because (in the worst case) when you tried to figure out
what has been done on a C++ program. The answer was already precomputed by
the compiler on the author's side. So you never get the algorithm.
For example,
If someone knows how to optimize code
int main (int argc, char *argv[])
{
int i,j, k[10];
i = 0;
j = 20;
i = j * 3;
return 0;
}
What you will get when you "debug" the program
push 0x3c (60)
call printf
So you get nothing out of it... needless to say .NET which is a stronger
compiler than ever.
So It is the most secure to write code in Win32 environment since all the
info is destroyed
The above is my personal opinion!
compilation. After some study, I draw a conclusion that "reverse
compilation" is completely blocked off in win32 environment (except in .NET
languages like C#) because (in the worst case) when you tried to figure out
what has been done on a C++ program. The answer was already precomputed by
the compiler on the author's side. So you never get the algorithm.
For example,
If someone knows how to optimize code
int main (int argc, char *argv[])
{
int i,j, k[10];
i = 0;
j = 20;
i = j * 3;
return 0;
}
What you will get when you "debug" the program
push 0x3c (60)
call printf
So you get nothing out of it... needless to say .NET which is a stronger
compiler than ever.
So It is the most secure to write code in Win32 environment since all the
info is destroyed
The above is my personal opinion!