Protect! EXE/COM v.4.0+ - Encrypts & protects
your EXE/COM files. Does a CRC file integrity
check whenever they are run. It now includes
a POLYMORPHIC ENCRYPTION ENGINE to mutate the
security envelope and to provide even greater
protection against MODIFICATION, HACKING, and
REVERSE ENGINEERING of your programs. Overlay
support & load times are upto 4 times faster.
Req: PKLITE (R)/LZEXE/etc. for best security.
Protect! EXE/COM v.4.0+
(C) 1993 Jeremy Lilley
All Rights Reserved
Thank you for obtaining Protect! EXE/COM v.4.0+ to evaluate.
Please read through this file and read about all of the new changes
in WHATSNEW.DOC before using Protect (if you are new to Protect! or
want to use Protect! optimally, you should read the documentation).
The syntax for Protect! is:
PROTEXCM MYPROG[.EXE or .COM]
If no extension is specified, it will try to search for the file.
Protect! EXE/COM v.4.0+ requires that you compress each EXE
file (this is not required on COM files) with an EXE file compressor
such as LZEXE, PKLite (R), Diet, Compack, etc. in interests of
providing the maximum security for your files.
If you're unfamilliar with Protect!, it is an encryption
program for EXE/COM files that scrambles the files and stores a
CRC, which is a value used to check the file's integrity, on its
mutating security envelope. When you run a Protected file, it will
decrypt itself and check to see if it has been modified, possibly
by a hacker or virus, and if it detects modification, it stop and
return a user-defined CRC (file integrity) error message. Using
anti-debugging techniques and security envelope mutation to protect
tracing and hacking as well as highly-optimized encryption/
decryption routines, Protect! EXE/COM is an excellent security
Anyway, the most important new feature is the POLYMORPHIC
ENCRYPTION ENGINE which mutates the security envelope every time a file
is encrypted using Protect!, which is like having a different version
of Protect! to use for each file you Protect. Hopefully, this should
end the cat-and-mouse game involved between cracking utilities and new
versions of Protect, and take Protect! out of the realm of "crack
one, crack 'em all" protection utilities. If you try Protecting a file
several times, the file size and the security envelope will be
different each time because of this mutation.
If you are testing Protect! by Protecting a file and then
modifying it, please note that if you modify certain spots, you
will wind up crashing the file before it gets to the file integrity
check. Also, in some files, particularily at the beginning of EXE
files that were PKLited before being Protected, there is some
"dead space" that cannot be checked for integrity (due to the fact
that it is a portion of the EXE header and not read into memory).
In the instances that it occurs, this "dead space" is just a series
of random bytes that just *incidentally* cover up PKLite (R) and
other copyright messages.
Also, Protect! is $25, and in order to distribute files
that you Protect, you must register. Registered users get a copy
of PROTEXCM.EXE without the beg screens, the ability to define
your own CRC error messages, updates, support, and more.
27816 Radfall Court
Santa Clarita, CA 91350
Internet: [email protected]