[snip] Too easy...the client would just have to check the code for it and he would have the code.
Better get a md5'd version of the code from somewhere in the net (from your server for example) and compare it to the md5'd version of the code the client put in. But that way the client could always just comment out the if condition. Hmm..maybe you can obfuscate that somehow...but I've no idea if that's possible in php...? [/snip] Assuming the client can read code, but I agree with encrypted code. As for obfusation..isn't that what we live for? :) How about a series of functions that call each other, comments in the code that don't tell the whole story. Name the variable for the unlock code something non-obvious. Check the date and set a variable that seems in concert with the application. Bury functions within other functions. Nest if statements to within an inch of their life. Wait....I just read some code like that that was due to lack of planning and documentation...and there is no self-destruct mechanism...just 'spaghetti' code! :) The legal angle should be the one most considered. That and having a contract. Jay -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
