2

I searched, and only found a couple([1][2]) of answers here. None of them really answer my question though.

My application will have a thirty day trial period. What's the best way to protect the program? I'm not worried about crackers, just Joe Average reinstalling the program. Setting back the clock isn't really a concern either.

Community
  • 1
  • 1
Jonah
  • 9,991
  • 5
  • 45
  • 79
  • 1
    Can you go into more detail about why the linked solutions don't do what you want? – unholysampler Feb 27 '11 at 19:10
  • Keep in mind that it will be super easy to deompile the .class files and remove the offending code, even if you obfuscate it. – Chris Feb 27 '11 at 19:12
  • possible duplicate of [How to prevent a Demo Java Program from my client's regular use?](http://stackoverflow.com/questions/2146315/how-to-prevent-a-demo-java-program-from-my-clients-regular-use) – Don Roby Feb 27 '11 at 19:15
  • 1
    @Chris: While that is true, he said he was not concerned with hackers, just everyday people. – unholysampler Feb 27 '11 at 19:27
  • @unholysampler: the first one requires hardcoding the expiration date into the source. The second has the same problem, and others that require connection to the internet to start up. I just want to require connection for entering the keys. – Jonah Feb 27 '11 at 20:20

1 Answers1

3

Here's exactly the question you're looking for:

Implementing a 30 day time trial

Community
  • 1
  • 1
SyntaxT3rr0r
  • 27,745
  • 21
  • 87
  • 120