close

Discovered in

glancast

glancast
1,107 Favs

Find other sites about

Related Sites

  • Showing 7 of 13
  • Reviews of the site
  • Join StumbleUpon or login to add a review! default avatar

  • Rated by tlacy on Feb 03 2009, 6:54pm

    First, this is trivial to find and disable - if not by the customer, then at least by any competent developer hired to replace the idiot who wrote this. Second, if I caught a contractor pulling a stunt like this, I'd see them in court. Finally, isn't this what contracts are for? I'm appalled that anyone thinks this is a good idea.

  • Reviewed by bossjet on Feb 02 2009, 10:17am

    Nice idea.

  • Rated by SuperFreak69 on Feb 01 2009, 8:57pm

    Very cool idea.

  • Rated by iamquarry on Feb 01 2009, 8:30pm

    try being a better contractor first, write better code 2nd.

  • Rated by csocci on Feb 01 2009, 8:03pm

    Lame. If you seriously think you need this, either your work sucked, or your contracts and business skills are on par with a 10 year old's.

  • Rated by aeris311 on Feb 01 2009, 7:36pm

    kill switch, awesome

  • Rated by Downlord on Feb 01 2009, 3:32pm

    I thought about doing this in many other variations, coming to the point that at the end, they will get some student to get rid of that "protection" in a minute. This "trick" just requires you to do a text search of the displayed message to find the correct file. Then you just eliminate those lines whiche are responsible for it. Allthough I think combinating this with protecting your code with let's say Zend Guard could work. The author should have mention that. Also it's a totally waste of bandwidth to let the script ask for permission, even after the client has paid. Some script should be able to overwrite the existing home phoning script (and deactivating the "kill switch"), after payment is done. Aaaand: As a customer I wouldn't be happy, to see a message on my company website, that I'm owning someone money. Just imagine what would happen, if the "license" / "permission giving" server is not responding, due to some technical problems? BTW: One of my "solutions" was, to activate the kill-switch manually, by sending a Request containing an unique deactivation code. So I could be able to deactivate a website, by just opening the website a la "http://www.mycostumer.com/?deac=134#24Gs7a3..........". This could trigger a script to rewrite and modify the main script, or set some flag in their database. This way the costumer wouldn't be dependant on the availibility of my "licensing" server. But as I said before - without encoding your PHP scripts, this is just too eays to crack.