That was merely an illustration of how powerful obfuscation is, and what a cracker is up to.It's true, especially on assembly language it's not very effective. However his code is also using a virtual machine.
The obfuscator I intend to use is of course for assembly language, not source code. :roll:
Anyways, here's my plan for my SYSTEM so far:
Since my main protection is an obfuscator, the critical parts of the code is changed into
instructions which will run on multiple VMs
Customer pays for a licence and supplies his name and email
You enter his name and email into the licenence system
The licence system randomises name and email, fingerprints this
to create a serial
The licence system composes a mail with his registration details and
mails it off to him
The customer enters the registration details (name, email & serial)
into the program to register it
The program randomises name and email, fingerprints this and
compares it to the supplied serial
If ok the program puts the name and email in the about box
The program writes the registration details to a file
On startup, the program looks for the file, if not present, the
program is unregistered
If found, the program read name and email, randomises name
and email, fingerprint this and compares to the serial found in
the file (auto registers on each startup)
If ok the program puts name and email in the about box
If file not found or not ok the program is unregistered
...
- The randomise and compare methods are protected by the obfuscator
- When you receive the payment details from PayPal, you simply
enter them into the Licence System which compose a registration detail
mail body you can mail off to the customer
- The customers enters these registration details once and thats it
- If he decides to share the app with the rest of the world, he also shares
his name and email with us
)