You should never use ordinal home users as your target auditory for selling. OS level protection - is not 100% safe, but still better, than homebrew license protection. That's why locked smartphones - are most safe way of content distribution now. Only some sort of hardware protection may give you 100% confidence, that you're safe.
Braking license protection should take large amount of time, very laborious work and have big chance of braking some functionality of your program. But your code should be literally infested by license verification checks, hidden everywhere, in order to make it as hard for hackers to brake it, as possible. You should use open key, built via using computer configuration, to decrypt license information. This encrypted license data is then used as "activation code". Your license server uses computer configuration to build secret key and encrypts some license data via it. You use computer configuration to build some sort of open key. It's usually about using something like asymmetric encryption. Standard license protection usually means, that there is "standard" way to break it. Better safe just means it would take more time to brake it's security, so it requires constant updates and leads to some sort or arms race. As I know, you pay some fee there - you get standard built in protection. Info from coders with real life experience selling their apps on-line wd be the most pertinent. Does anyone use either of these? What about Shopify? Paypal? (is only a form of accepting payment, I think). These two companies now seem to deal more in bigger SaaS products. My app is tiny, only $8 CDN, and is meant to be downloaded and run locally on a server. Now I'm not sure if either of these are what I want.
Or should I come up with my own cockamamie method of planting some secret key in the Registry? I'd like it so that once a license is granted, it's tied to a machine (and a user account), and it cannot be transferred.īack in the day there were two big software distribution companies, ShareIt and DigitalRiver. App target OS: Windows onlyĭoes anyone have recommendations about what to put in my code for licensing enforcement? Is there a standard component that I can plop onto my main form and give it a GUID and somehow set it to: "Don't run unless you have a license for this GUID" (which might be another GUID?). App was built on platform: Lazarus 1.8.1, FPC 3.0.5.