Unlocker and demo mode
@Christoph-Hart Is there a safe way to run a demo mode using the unlocker?
I imagine if we just use the unlocker to set a bool that engage/disengage some demo safeties it doesn't make much sense...
Or the only way is to export a separate binary?
@ustk Interested in this topic.
@lalalandsynth I don't know yet to how to... But I assume it might be straight forward once we get the expiry process of my other post https://forum.hise.audio/topic/7098/unlocker-expiring-date sorted.
My guess is to run some demo restrictions in the plugin if an expiry date is detected with
If one wants a perpetual demo though (just with some restrictions inside) then it's dangerous. Because you probably have to set a very long date that will never be reached, but then the plugin would exposed to an easy hacking. So I would suggest that perpetual demo have to be exported separately.
@ustk yes that's precisely the use case - full functionality with an expiry date that is embedded into the license key file and checked against a trusted timestamp (from your server) so that the user can't just change the system clock to bypass the expiration. The check is not done on the HiseScript layer but in C++.
This is a bit difficult to setup on the server side which is why we are offering this as service at https://activate.hise.dev which we have launched silently last month.
@Christoph-Hart Intersting! For now I have everything working except that expiry date in my other post...
(sorry for double posting I didn't remember asking on the topic before...)
@Christoph-Hart Is this up and running?
We have a product out very soon and bought a HISE license.
Would love to incorporate this.
Is it more secure way for the hackers?
There's some more info about the technology behind it on this site, but yes I expect it to be significantly harder to crack than just a copy protection on the scripting layer (although it doesn't claim to be as secure as iLok and other companies who have that as their single business concept).
Is this up and running?
Yes it's functional and already in use by one company. The signup process for the developers could be more straightforward, but the end user side works as expected.
@Christoph-Hart I've read someone got the juce unlocker hacked by brute force of the key which I thought to be near impossible. So they moved to a 2048bit key.
My thought is that if the only thing they could do is a brute force, that means the binary is secure enough.
Any thought about this key length?