Trial Version
-
Hi ,
I wonder the method of programming to make a plugin as a trial version. Is there any technique to add in a code , isn't it ?.I'm an architecture student , and I got a comment to do for a company testing.
Pink
-
It needs to be compiled as rbs, otherwise what it's doing in an rb is easily read and circumvented by the unscrupulous.
Time limited:
Check if the script is already licensed - perhaps a .lic file with it or somewhere on the computer.
If so skip any more checks, else...
Get the time/date the script is first run.
Store that in an encrypted file somewhere in a read/write-able folder in something like the AppData tree, or write a non-obvious Registry-entry.
Every time the script runs check the time/date against the stored value.
Perhaps remind [nag] the user of their remaining time?
If it is > time-limit tell user and exit, else continue...Usage-count limited:
Similar to above...
Check if the script is already licensed - perhaps a .lic file with it or somewhere on the computer.
If so skip any more checks, else...
Set a counter in a file somewhere etc, and decrement its entry every time the script runs.
Perhaps remind [nag] the user of their remaining uses.
If it is < 0 tell user and exit, else continue...You can also have the script 'check-in' to a server on the WWW as it runs, and compare the current user against listed-licensee - this allows time-limited licenses too, and can prevent copying of licensed versions between computers - but it's perhaps a little draconian for a relatively inexpensive script
-
I'm so grateful TIG , I will study later after I finished evaluation forms. You are a very good mentor. Respect You.
-
Keep in mind that there are rbs unscramblers on the internet, so it's not 100% safe either.
@tig said:
It needs to be compiled as rbs, otherwise what it's doing in an rb is easily read and circumvented by the unscrupulous.
-
But for a low cost script decrypting an rbs to see how it is licensed hardly seems worth the effort.
In contrast simply reading a plain rb is much easier to do and more likely to lead to a license breach.
Encrypting data/licenses is never going to be 100% 'hacker-proof' - but neither is your front-door lock - but you'll have one and use it anyway - just to stop a casual intruder walking in and stealing your laptop - but a determined thief will know how to open most locks - or just enter another way...
Advertisement