RE: [PHP] Self Destruct code
| From: | Jay Blanchard | Date: | Tue, 07 May 2002 11:41:11 +0000 |
| Subject: | RE: [PHP] Self Destruct code | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-96398@lists.php.net to get a copy of this message | ||
[snip]
I have a funny request; I wrote a system for a client and am rather
concerned that I am not going to receive payment for the work done. They
want me to hand over the code before they are willing to pay, so
basically I will be left at their mercy; if they don't pay, they will
still have a working version of the system...
So, is there any way I can inconspicuously code in some boo-boo's that
are time related etc. Something that will bomb the mysql tables or break
some code if it is not "unlocked" within a month etc.
I'm not sure if people out tjere might have existing safeguard tools
etc, so I'm open for suggestions.
[/snip]
You could try something like this;
if(date == '30 days from now'){
if(unlock code <> 'the unlock code'){
Do stuff to disable code, set variables to odd values, drop tables,
whatever;
Do stuff to send e-mail to offending party;
}
}
HTH!
Jay 'Been There, Has to Do That' Blanchard