I have checked the U-He web page and they have this to say:andy-cytomic wrote:As already state lots The worst case backup plan is to release a command line program that runs on your local machine that will generate any number of auths. This is built at the same time, and with the same code, as each plugin release. You will always be able to authorise your software, either through an online server that is still kept running, or a local program.djanthonyw wrote:I would very much prefer a standard serial or license file based form of copy protection (U-he, PSP, 112db, ect) if the current form can't be used anymore. I tend to stay away from dongle and C/R whenever possible. Being able to reinstall my software without contacting anyone (auth limits, ect) is important to me and I would hate to have to stop using and sell my current licenses because of this.
I do trust your ethics Andy, but there are countless examples where customers are left out in the cold due to this type of dependent copy protection after a company closes up shop (even after they promise it won't happen).
I have contacted Urs to ask how he limits the number of installs for each serial / auth file without involving a server. If he can provide a secure and difficult to crack answer then I will do use it, but that won't be until after this first release as it will delay things further. I am not sure Urs' system offers this functionality, which will mean I can't offer educational and studio site licenses which is really important to me.djanthonyw wrote:IU-he seems to have very effective serial number copy protection that is aax compatible. Have you considered contacting Urs about it?
"On how many computers can I use my u-he licenses simultaneously?
Licences for our products are issued to you as a person, not to your machine(s).
So you can install, activate and use your u-he products on any computers *you* personally own without having to purchase extra licenses - as long as *you* are the one using them.
Also, we don't differentiate between Mac/OSX and PC/Windows, one license covers all."
So this to me looks like there is no way to limit the number of authorisations possible, so this aspect of his system does not meet my requirements. I do use many methods that Urs has suggested and documented.
I will still let you know what Urs says via email on the topic of how authorisations can be capped without using a server.
