Having an executable expire

[bseguin]

A harder way to prevent hackers, is to put in an external file a counter that change/increment. if that file is modified or recopied, you can detect that by adding a CRC check. The best is to add multiple feature that makes the hacker lost in the way you do it.

-Windows registry check

-Windows file installation (if current clock is older than a specific file date, then lock)

-Your own external file that you modify with the installation date and current date... if date mismatch lock

-Internet time match current computer

-SMTP server time check

Your imagination is the only stopper for this kind of security.

Design one that is multiple check and then you should be ok.

Benoit

[wiebe@CARYA]

Hackers love a challenge .

How about installing in a VM? Problem solved (the hackers problem that is).

Think about your audience. How likely are they to hack into your application? If you put it online for everyone to download you might give it some though. Even then, the LabVIEW community isn't that big, your audience smaller, and the nr of hackers even smaller, the nr of hackers willing to put the hack online close to 0.

How bad is it if 1 of 1000 (or 100) users hacks your application? You might lose money, but how much? I'd say almost always every effort to protect beyond the minimum will be a waste of your time and money. But I don't know your numbers...