Yes, TurboActivate handles different types of client-side fraud (including "clock rollbacks").
I want to authorize my application to run for a month or for a year, but the computer will rarely be connected to the internet. I don't want the user to be able to back-date the clock on their computer (in the BIOS, before Windows starts) and stay off the internet, and just keep using my application forever.
I had expected to use a hardware dongle containing a real time clock for this to work.
Does LimeLM have some way to handle this situation?
Yes, TurboActivate handles different types of client-side fraud (including "clock rollbacks").
That's great news -- thank you!