Like most of you here I suppose, I have this code:
(code changed for obvious reasons!)
Should I hide my unlock code in any way?
asked Nov 10 '12 at 09:28
In the CkString C++ class, there are two methods: obfuscate and unobfuscate:
You could use the obfuscate method separately to produce an obfuscated string, which can then be placed as a string literal in your application. Your app would then call unobfuscate, and then pass the unobfuscated string to UnlockComponent.
In any case, Chilkat would not invalidate your unlock code in a future version without notifying you first. In the 10+ years that Chilkat has been in business, no unlock codes have ever been invalidated for the reason you described. Unlock codes have been invalidated for other reasons, namely (1) unlock codes generated by non-Chilkat parties, or (2) unlock codes delivered to fraudulent orders.
answered Nov 12 '12 at 08:50
I have never obfuscated those unlockcodes but you made me think (on a sunday morning).
If my unlockcode leaks on the internet and pirates start to use it Chilkat's only option is to blacklist my unlockcode for future builds, who can blame them. My programs will continue to work (because they use the "old" ck libraries), but when I do a new release I need to ask Chilkat for a new unlockcode.
I will add it to my "to do" list, I guess a trivial obfuscation is enough, something like strrev().
What is your opinion on this, Matt?
answered Nov 11 '12 at 03:24