Insite Designer 
How not to protect 
- by PIrgE
This is a post for programmers really to highlight how not to protect.
Insite Designer is a really nice html wysiwyg editor with a big nag box asking users to pay for the full version.
I understand that they want people to buy the software but they have broken all the protection rules:

the three protections and the workarounds are:

1. nag box TrialWIndow - change first line of the constructor function of TrialWindow() to return to stop it showing.
- patch a jump in the app destructor before it sends the "destroy trial window message" to stop crash on close

2. inserts text at the end of every file it saves identifying the software and version - hex editor

3. no saving - find the save function and patch a jump before the alert - you go to save function rather than alert then jump out

The three rules they have broken are:
1. if you don't want users to have certain functionality REMOVE the functionality from the executable - i cannot stress this enough
2. don't have one function that your protection relies upon (the trial window consrtuctor in Insite Designer)
3. don't have plain text strings in the executable that are part of the protection

PIrgE