vectorjae.blogg.se

1. #ZEND STUDIO SERIAL KEY LICENSE KEY#
2. #ZEND STUDIO SERIAL KEY SOFTWARE#
3. #ZEND STUDIO SERIAL KEY CODE#
4. #ZEND STUDIO SERIAL KEY LICENSE#

#ZEND STUDIO SERIAL KEY LICENSE#

This way, all licenses are checked every 30 days, and we don’t overload the server too much with license check requests. Once the 30 days have passed, the next login simply repeats the process. That’s valid for 30 days, and is used instead of the phone home. Then, a local key file is generated, which we store somewhere in the app’s path. We’ve basically set it up so our app phones home whenever a user logs in. We use IonCube in combination with Iono - Iono handles all the license stuff for us, including the phone-home stuff. Hopefully its not that complicated to do.

#ZEND STUDIO SERIAL KEY LICENSE KEY#

You would have to do some PHP coding for that though, but it would be interesting and you’d have a powerful setup once done.įrom what I understand from their reply, I can dynamically generate a license key for every customer but I have to do the coding myself. Programatically, and so it would be possible to even automate the sending There’s a command line tool for creating licenses that could be run If you use our licensing system, you could just send them a new licenseįile. > each customer? I just don’t wanna do it manually you know what I mean?

#ZEND STUDIO SERIAL KEY SOFTWARE#

> software after 30 days? Do I need to generate the new license file for So I have to send them another copy of the That didn’t believe it and it could damage the product. Personal details were transferred between machines, there would be those The system was very specific, limited in functionality, and that no We have considered putting in these features to the Loader, however the Provide evaluations,Īnd say that customers should take advantage of the evalations toĭetermine whether or not your product is for them. Note though, that this is not enabled on some servers, and so you couldĪnother alternative is simply not to allow refunds.

#ZEND STUDIO SERIAL KEY CODE#

Period has passed and where they can no longer have a refund.Īlternatively, you could code in phone-home type idea using URL fopen. Say 21 days, and then replace their license with a new one after that Term expiring license that runs the length of the initial refund period, You cannot physically remove license files, and we don’t provide any > Can your software do that? Can I automate this process on my web site > right to remove the “license” so that they can’t use my script anymore. > they choose to refund their purchase after X days, I will reserve the > “register” their script so that they can use it on their web site. > Let’s say I wanna sell a PHP script and I want my customers to Lots of companies do this and there’s nothing wrong with offering more choice to your users

If you have the cash available, then you might want to consider offering both an ionCube encoded version of your script and also a Zend encoded one. ionCube (and SourceGuardian) include methods for generating license files as well which should also be useful to you - with Zend you need to purchase their SafeGuard suite at $6000 or so to do that.

It’s secure, well priced from only $199 and Nick and his team are extremely good at supporting users. Out of all three, I would recommend ionCube to you. The features in SourceGuardian are roughly comparable to ionCube’s, so it’s well worth a look. Adrian and the other people at SourceGuardian are happy to admit prior mistakes and talk about what happened, so if you are concerned then you shouldn’t hesitate to drop them an email. SourceGuardian v4 is a lot more secure than previous versions (which could be returned to some form of source).

This gets you Zend Studio and Zend Encoder for $395 (and then $295 every year) which are both excellent applications. If you like the look of Zend but the price is the only thing that puts you off, you might want to take a look at their Small Business Program ( ). Read the “How secure is it?” from their FAQ to hear that in their own words. The reason it’s so cheap is that it’s stupidly insecure. You could interpret experienced to mean "is able to replace eval with echo!"Īs I said then, if you're serious about protecting your code from prying eyes then I would stay well away from any PHP based encoding system. "The fact is, any PHP encryption program does needs to decrypt the file at some time, so the code will theoretically be available to experienced crackers during its execution." "Codelock for PHP is a strong deterrent." I wasn't impressed then, and I'm not sure much has changed. I briefly looked at codelock a year ago, responding to a couple of threads: IonCube also have an online encoder, which can work out fairly inexpensive for small projects (btw I don’t work for IonCube). I really would advise you to look at Zend or IonCube (SourceGuardian may compile to bytecode these days, I’m not sure).