yet another simple serial protection system
Posted: Sat May 03, 2014 12:38 pm
This is yet another simple protection system.
I find it interesting for other needs, but may be helpful for you.
How it works?
Array of chars (letters, common signs, case sensitive) is ued.
Each letter is assigned to random number and re-randomized array of input chars.
Thus - each letter is encoded as ##$, that is 2-digit number and single mark.
For creating matched keyfile - only first two and last two chars are used (you can extend it).
So if you have "abcdefg" username, then keygen will use a,b,f,g letters.
Chars are encoded to the formula ##$##$##$##$, that is - number-letter pairs.
Then you need to create the keyfile with username and serial number (can be automated from schematic).
And now the trick, how you can use it.
1) User is asked to enter the key.
2) If username and serial number match - keyfile is saved.
3) At the same time - indicator(s) is/are saved in some secondary options file (under the name of some unused gui setting).
4) On load - program should check the keyfile (whether the username and serial number match) AND the indicator(s) in options file.
Benefits:
Since username and serial number must match (to some degree - user does not knows to what degree) - you have the control over the data you associate with the serial number in keyfile. It's a psychology.
If you use the trick (indicator) - copying the keyfile only - will not activate the app. And your options file may be stored or hidden somewhere else than your app.
User/keyboard friendly (sometimes needed) serial number (can be entered manually).
*
As you can see - it's not complicated. It uses more of psychology than hi-tech.
John Smith
32m12x56p01!
I find it interesting for other needs, but may be helpful for you.
How it works?
Array of chars (letters, common signs, case sensitive) is ued.
Each letter is assigned to random number and re-randomized array of input chars.
Thus - each letter is encoded as ##$, that is 2-digit number and single mark.
For creating matched keyfile - only first two and last two chars are used (you can extend it).
So if you have "abcdefg" username, then keygen will use a,b,f,g letters.
Chars are encoded to the formula ##$##$##$##$, that is - number-letter pairs.
Then you need to create the keyfile with username and serial number (can be automated from schematic).
And now the trick, how you can use it.
1) User is asked to enter the key.
2) If username and serial number match - keyfile is saved.
3) At the same time - indicator(s) is/are saved in some secondary options file (under the name of some unused gui setting).
4) On load - program should check the keyfile (whether the username and serial number match) AND the indicator(s) in options file.
Benefits:
Since username and serial number must match (to some degree - user does not knows to what degree) - you have the control over the data you associate with the serial number in keyfile. It's a psychology.
If you use the trick (indicator) - copying the keyfile only - will not activate the app. And your options file may be stored or hidden somewhere else than your app.
User/keyboard friendly (sometimes needed) serial number (can be entered manually).
*
As you can see - it's not complicated. It uses more of psychology than hi-tech.
John Smith
32m12x56p01!
