Protecting .EXE files


 Rescue5 supports two methods of protecting .EXE files:

 1) In the procedure called "ERRORSYS" create a memvar (a
    private, public or auto (undeclared) variable) called
    "ERRORSYS" with the numerical value 9876543210.

 2) Use Blinker to "burn-in" a demonstration date or
    demonstration limit into the .EXE file that exceeds the
    likely life of the system.

 If Rescue5 detects either of these methods it will refuse to
 decompile the .EXE file.

 There is currently no method of protecting a single procedure,
 or group of procedures.

 APTware is working on a general security and encryption tool
 that will protect code at procedure level, preventing any
 decompiler from recovering code from protected procedures.
 This tool will be suitable for protecting third party library
 code without disallowing the recovery of other code linked into
 the same system.