Menu
Currently, I do a database check every time a client opens my application — they enter their login information, and my app then runs their info through the database and see if it matches. It works flawlessly, except that this method won't do me any good if I am creating software that does not use the Internet (hence, I cannot always expect that the user is connected to the Internet whenever they press the login button).
To do the initial license check is no problem, however once the details have been verified once on the user's PC, I suppose I need to store something locally to check for the next time the user opens my application.
How do you go about storing licensing data locally? I have been reading up about it, and apparently decrypting the license data is a big no-no, if I want to avoid keygens. Do you use the registry, or a file?
865
Typically, the primary license file is stored in the application directory or created on first execution in the application folder or the registry, one or more aliases are stored in the Windows Registry, Windows, or Windows\System(32) directory.
Licensing is a key part of sales and financial growth, but first and foremost it's legal protection for your intellectual property. That's why it's important to understand the legal categories that include most licensing models: they're the foundation for your monetization strategy.
Software licenses typically provide end users with the right to one or more copies of the software without violating copyrights. The license also defines the responsibilities of the parties entering into the license agreement and may impose restrictions on how the software can be used.
Storing license information in a file or registry is fine. But you have to decide if licensing the software licenses it for
That decides if you have to store it for all users (HKLM, CommonAppData) or just the current user (HKCU, AppData).
Both are fine.
i suggest that you don't be stupid go overboard. Don't tie the license information to hardware keys, MAC addresses, serial numbers - because then i lose access to my own software when i change computers.
It's good enough to have a encrypted, signed, base-64 encoded license file, that contains their Name and Company.
180
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
