RE: [PHP] Self Destruct code

Does it have to be a booby-trap or will some little annoyance like a shareware popup that would just aggravate the heck out of them do the trick? Robert W. Collins II Webmaster New Orleans Regional Transit Authority Phone : (504) 248-3826 Email : rcollins@norta.com -----Original Message----- From: Cal Evans [mailto:cal@calevans.com] Sent: Tuesday, May 07, 2002 10:15 AM To: PHPCoder; php-general Subject: RE: [PHP] Self Destruct code IANAL! It's against the law in most states to create booby-traps in your code. As others have suggested, don't turn over the code until you've received payment. IMHO, you really should have specified the payment schedule in your contract. =C= * * Cal Evans * Journeyman Programmer * Techno-Mage * http://www.calevans.com * -----Original Message----- From: PHPCoder [mailto:internet@vsa.co.za] Sent: Tuesday, May 07, 2002 3:20 AM To: php-general Subject: [PHP] Self Destruct code Hi 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. PS, I know about Zend's encrypter, but since it will live on their server, I don't think it will help much since they will need the decrypter on there anyway right? Thanks -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php