14 replies
by yoginc Accepted solution
by yoginc Accepted solution
by brian Accepted solution
by seanferd Accepted solution
by robo_dev Accepted solution
My experience has been that typically you can trace the program logic, and maybe sorta figure out what modules do what, but it's like turning sausage back into a pig....rotsa ruck with that.
The more useful thing often is to run the program in a debugger, but I digress.... I've used a tool called IDA Pro, PE Browse Pro, and a whole raft of others I cannot remember.
by seanferd Accepted solution
by yoginc Accepted solution
by seanferd Accepted solution
by peconet tietokoneet Accepted solution
by the 'g-man.' Accepted solution
by robo_dev Accepted solution
In terms of reverse-engineering, you cannot really get the source back from compiled code; it does not work that way. While there are some things that it can figure out if it's a very simple program, at most it's hit-or-miss. And don't forget that these tools are made for one specific program...you need a decompiler specific to DOS executables, and a specific one for flash, etc. etc.
What I've seen is that you get back are some snippets of code, which give you a rough idea of the program flow. If the program is security related, or the developer does not want it to be hacked, he/she can use encryption and a great deal of obfuscation to frustrate any attempts to decompile and steal the code. And on top of that, what you can end up with is like 100,000 lines of un-commented and incomplete code...a real pain to work with.
To clarify, a disassembler is a computer program that translates machine language into assembly language, while a decompiler attempts to return machine code all the way back up to source code.
by yoginc Accepted solution
This discussion is closed to new replies.
Trending Software posts
Sort by Trending