I'm wondering what some of my fellow developers use to combat piracy, except for obfuscation. I'd appreciate a private conversation about this (for obvious reasons).
That wont really stop the problem though, especially for private transactions, say between two friends? Then you have the leak forums.Just keep proof in the work of it to show that you've made it first and own all rights well to have made it.
I'll have to check it out!Use advanced license, it's a licensing system for plugins that you can use. It's a free resource on spigot, it was supposed to be premium but spigot doesn't support the licensing system type things.
I don't think I'd want to encrypt and decrypt byte code on the fly like that though. Although that's on the right track, I'm certain a server would be required.Advanced license is way too easy to bypass, yes you can fight piracy, but it's difficult. Anyway this is how you do it
You have your core plugin, a plugin that takes care of your other plugins. And a backend server. Now you need an encrypter that takes 2 keys, secret string from server and license code. And a plugin. Now that you have all of those you encrypt your plugin. And get the decode key from server which is done during runtime, if a license gets deleted, the plugin no longer can be decrypted and it will lock itself out. Yes I have this system it took me a long time to make it and I'm planning to release it but it will take a long time till it will actually be suitable for production use
Definitely not true, I have my own proven system.There isn't much you can do about it. If you want to release a plugin, just expect it to be leaked and used. If not, don't release anything.
Definitely not true, I have my own proven system.
Can't do much to prevent decompilation except obfuscation, in that sense their isn't much anyone can do.Uh
*takes the jar*
*throws it in a live java bytecode editor*
*removes validation part*
*shows finger*
Bytecode encryption is fun.Can't do much to prevent decompilation except obfuscation, in that sense their isn't much anyone can do.
Anything can be pirated, stopping the average pirate is the goal. Something to keep people from sharing it with others or their buddies is as much as most could ask for.[DOUBLEPOST=1464113948][/DOUBLEPOST]Uh
*takes the jar*
*throws it in a live java bytecode editor*
*removes validation part*
*shows finger*
Then they will decompile the classloader[DOUBLEPOST=1464114094][/DOUBLEPOST]You could compile the source code to machine code, and not worry about encryption with the same results.Bytecode encryption is fun.
Yes you can encrypt them, but you need a custom URLClassLoader for it
Not if they can't get the secret key from the serverAnything can be pirated, stopping the average pirate is the goal. Something to keep people from sharing it with others or their buddies is as much as most could ask for.[DOUBLEPOST=1464113948][/DOUBLEPOST]
Then they will decompile the classloader[DOUBLEPOST=1464114094][/DOUBLEPOST]You could compile the source code to machine code, and not worry about encryption with the same results.
They can remove that part of the class loader.[DOUBLEPOST=1464114286][/DOUBLEPOST]Adding a server license check like mine, then compiling to machine code instead of java bytecode I believe would be the best solution.Not if they can't get the secret key from the server![]()