Different Encryption Types in HISE?
-
I also suggest taking a look at this which definitely helps consolidate everything into a nice blog post:
-
@Casmat said in Different Encryption Types in HISE?:
@d-healey yup haha, I had seen the same thing, the thing with keygens is that everyone’s starting to realize that using encryption is the way to go, and keygens have died down because these cracker groups are unable to find any way to get real keys
No, the keygens definitely didn't die.
I guess you haven't seen industry-leading plugin manufacturers that have been hacked even though they used cutting-edge encryption methods in the market.
The logic of keygens is not just finding existing keys. It can also solve Key's mathematical formula. Or a fake little server like app can cheat the plugin via The HTTP 200 OK success status response. Then it generates keys upon the method. In this case, it makes no sense whether to encrypt the key.
In my experience, if the licensing system used by the plugin is not obfuscated, it will definitely be cracked, regardless of whether the encryption is 2048. Because the hackers can see the source code very clearly, I guarantee it :beaming_face_with_smiling_eyes:
-
@orange said in Different Encryption Types in HISE?:
In my experience, if the licensing system used by the plugin is not obfuscated, it will definitely be cracked, regardless of whether the encryption is 2048. Because the hackers can see the source code very clearly, I guarantee it :beaming_face_with_smiling_eyes:
Yeah thats possibly another thing we need to think about - how do we obfuscate the HSIE script source code...
-
@Lindon you can't without encrypting it because anyone can just look at the code and make a deobfuscator. Security through obscurity is a last resort.
I take the approach that anything on the client side is already compromised so all my 'security' stuff is server side.
-
@d-healey said in Different Encryption Types in HISE?:
@Lindon you can't without encrypting it because anyone can just look at the code and make a deobfuscator. Security through obscurity is a last resort.
true. I bet you users love your "must have an internet connection" tho....
-
@Lindon They only need a connection to download the instrument, once they have the files they can use them offline, on any machine - remember all my stuff is open source so I don't have the same piracy paranoia as everyone else
-
@Lindon said in Different Encryption Types in HISE?:
I bet you users love your "must have an internet connection" tho....
I just released a plugin that currently supports online activation only. 35K active activations so far. 7 complaints.
I do plan on offering offline activation soon, but this doesn't appear to be huge issue like or was years ago. -
@Dan-Korneff said in Different Encryption Types in HISE?:
@Lindon said in Different Encryption Types in HISE?:
I bet you users love your "must have an internet connection" tho....
I just released a plugin that currently supports online activation only. 35K active activations so far. 7 complaints.
I do plan on offering offline activation soon, but this doesn't appear to be huge issue like or was years ago.Good to know Dan, thanks...
-
@Dan-Korneff said in Different Encryption Types in HISE?:
35K active activations so far
You should make a video tutorial about your marketing strategy
-
@orange ahh I didn’t think of that possibility, is obfuscation the only way to avoid this or what are some other methods you’ve used to avoid this?
And btw, your licensing system is amazing, we’re definitely planning on making something like it in the future:
https://forum.hise.audio/topic/4967/woocommerce-linked-licensing-system-for-your-plugins/2?_=1705339675044
What is the licensing app built on? -
@d-healey said in Different Encryption Types in HISE?:
You should make a video tutorial about your marketing strategy
As with any good marking plan, it all started with day drinking.....
-
@Dan-Korneff I'll have what you're having
-
@Casmat said in Different Encryption Types in HISE?:
@orange ahh I didn’t think of that possibility, is obfuscation the only way to avoid this or what are some other methods you’ve used to avoid this?
And btw, your licensing system is amazing, we’re definitely planning on making something like it in the future:
https://forum.hise.audio/topic/4967/woocommerce-linked-licensing-system-for-your-plugins/2?_=1705339675044Thanks.
Frankly, there is not much about obfuscation for now.
I think cracking the plugin depends on user demand. If it is a well-known company and it is a plugin that is really demanded by the users, the cracking of the plugins will take at most 1 week, sometimes 2 weeks.