On 16/09/2006, at 6:00 PM, Steven Hedgepeth wrote:
would someone please take a couple of minutes to explain why 128
bit encryption works for data but why it can't be applied to some
or all of the code of an executable?
Ultimately an executable has to be executed.
At that point it has to be translated into instructions that run on
the target machine. A sufficiently low-level debugger can be used to
intercept these instructions.
However, the page you linked to does actually suggest this as a
delaying tactic (nice link, thanks):
"Use encryption of any description, a simple XOR will add about 5
minutes to a crackers progress, commercial and secure schemes like
RSA/SHA/ECC etc. can add hours to a crackers progress, it is worth
studying the theory of some of these algorithms if you use them and
modifying them, since many of the algorithms use constants which can
easily be searched for in a disassembly listing."
and, implying similar:
"Pack your executable using a commercial or freeware packer"
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
