I’m probably stupid for going down that rabbithole, especially as I’m not very experienced in web development, but I also think it’s fun and interesting. It’s far too much effort if you just want to sell a plugin on the side. So it’s only viable if you plan to build a sustainable business around it. You want to keep the risk of frustration and support tickets as low as possible, so the policy should be as permissive as reasonably possible (in my opinion).īut you need to maintain a server and database for the whole scheme. However, be very careful about the exact policies and user experience around that. That way you can record the customer and purchase data in the database along with the serial key, and also bake some of that information into the key. You can set up payment services like 2Checkout or FastSpring so they request a new serial number for a purchase from the server via an API request. The nice thing about that is that you can limit check the number of activations per serial and thus detect if it is shared widely, and then blocklist it. The server then is the one to verify the serial number and activate the plugin (see the JUCE tutorial on this for a basic understanding of that communication). My currently preferred, but much more complicated solution, is to build a simple licensing backend server that handles serial generation and online activation. Nobody wants to be the name that shows up on every k’ed install. However you can tie it to a user name and display the user name in the UI like u-He does. But this way there’s nothing stopping anyone from sharing the key widely. That’s quite easy to do and you can use basically any shop system that lets you upload a list of keys. You’d usually use an asymmetric encryption scheme like RSA, where your keygen has the private key and the public key is embedded in your plugin to decrypt/verify the serial. The easiest way would be an offline scheme, where you generate a serial number that is verified by the plugin internally. I’m currently exploring the topic as well. Also, if you know of any books or other resources about the subject, please let me know. If anyone is willing to share how you handle licensing, I would be super grateful. For example, if the user downloads an updated version of the plugin, how can you identify that this guy already has a license for the product? I could go on and on about my concerns on this subject. Hardware-based IDs always become an issue when people need to reinstall or update hardware.”ĭue to my lack of knowledge in cryptography, this too is too general for me to start implementing anything. “A simple hashed code tied to their email or similar is probably good enough. Furthermore, generating keys from the user’s machine attributes seems highly case-dependent and frankly vague. Machine properties like MAC addresses, CPU and motherboard models, HDD serial numbers, etc., are either easy to change or commonly shared. Restricting the usage on other computers would require creating a unique machine id for each user, but this too has many pitfalls. I have seen many companies using a key file system, where you download a file to your computer to license the plugin, but I have no idea how it works and can’t find any information on the web. However, it is created mainly for WordPress plugins, and such not quite matching my needs. I will be using Easy Digital Downloads as a distribution solution, which has a software licensing addon. I’ve found few threads about the subject, but they are all more or less discussing the pros and cons of each approach. I know that everything worthwhile will get cracked someday by someone, so I wouldn’t want to spend too much time trying to come up with a perfect copy protection solution. However, the more I learn about the subject, the more questions I have. Besides, the library is frequently updated, so you will have more options in the future.For quite a long time now, I have been trying to search for a simple licensing solution for my first commercial plugin. Plenty of free assets to choose from For now, the built-in D5 Asset Library has thousands of free high-quality PBR materials that are ready-to-use.You can switch on rain/cloud/snow/fog with one click, adjust the skylight with HDRI or geographic sun, create high-quality PBR materials. 0 cost to set the environment/weather, edit materials/lights and do post-processing D5 Render provides an all-in-one visualization solution for free. Outputting 16k images/4k animations with no watermark ensures you the freedom to realize your inspirations at little cost. Create and render as many projects and animations as you need There's no limit to how many projects you can create with D5 Render.Free license does not expire, so you are guaranteed a safe and cost-effective rendering experience in D5 Render. You don't need a 14-day free trial or a limited version, D5 Render itself is free to use.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |