1. How secure will my scripts be?
We use various techniques to protect PHP scripts. This includes, but is not limited to, bytecode encoding, an encryption layer and obfuscation. Some of our techniques, for obvious reasons, are not documented outside of our team and this is to provide hightened protection for the PHP scripts. No system is 100% foolproof, though we strive very hard to ensure that we are at the forefront of PHP protection.
2. Does SourceGuardian include time limiting & IP/Domain locking?
Yes, SourceGuardian can time limit scripts either as part of the application or via a license file which can be generated. You can also limit to IP address, domain name as well as MAC address. This is standard within our application.
3. Can I mix encoded and unencoded files?
Yes. You can no problem mix encoded and unencoded files. So you may include encoded files from unencoded ones or vice versa. There are no problems building your PHP classes on other ones defined in encoded files, or having your protected classes derived from open source ones.
SourceGuardian has a special option "Script will work only with other encoded files" available on the "Lock" page in GUI or --conj option from the command line. When enabled SourceGuardian will restrict mixing encoded and unencoded files for better security. This option is off by default but you may turn in on if you use only encoded files in your project.
4. Can I lock my files to Internationalized Domain Names?
Yes, SourceGuardian can you can lock your files to Internationalized Domain Names (IDN). As internationalized domain names are transformed by browsers to ASCII using Punycode then you need to do the same with domain names you are going to lock your files to. There are websites that can help you doing that e.g. Verisign IDN Conversion If you are locking your files to multiple domains using wildcards, please convert the internationalized part of the domain name to Punycode and then add * and ? wildcards before using the domain name in SourceGuardian GUI or command line.
5. What is the best way to protect my code?
We always suggest that for the strongest protection that our users encode for the latest possible version of PHP and also use some of the features of the new version of PHP if at all possible.
We also suggest that our users look at locking to a license file. If you lock your files to your license file, generate licenses either online or offline for your customers then this will be the best method of protection. It makes sure that each customer is using a unique license key and it also means that it is possible to check who the owner of the license for any encoded software that appears on the internet along with a license file.
In addition to the above you can lock your files to IP/domains or better use encode-to-IP or encode-to-domain options for better security.
For any additional questions please contact support