Hi Klaus,
Before we talked and you say for krpano user side plugins protection for you will add additional key for all users to lock our developing plugins for everyuser different.
Any news for it.
Best regards.
New property for protect tool
-
Hi,
You can already check user krpano license username and email (_krpanolicense.regname & _krpanolicense.regmail), so you can build your own license key system based on those values. -
Hi,
You can already check user krpano license username and email (_krpanolicense.regname & _krpanolicense.regmail), so you can build your own license key system based on those values.Hi i dont mean this, for example you will bu a plugin from me, and i want it encrypted only you can use, you must send your register data to me and now one prefers this. We talked before Klaus, and asking him new edition will he add or not.
-
Well, email and username are not too touchy informations, the username is displayed in the krpano console ;)
This is what I do for my Callout plugin and it works well , the key only works with the user krpano player. -
as jerome said you can encrypt your plugin with the public key and inside check the regname / regmail of your client.
i do this for my plugins with each client getting a personal build. they don't work for another user.
securitywise there is no difference in what you're asking for, and ...
i wouldn't sell a plugin to somebody who doesnt want to give me his registration info
-
i do this for my plugins with each client getting a personal build
Maybe you should generate a key instead of a personal build ? Less work and much easier for plugin updates ;)
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!