As Royal Bg mentions in the comments, if they have the source code, there’s no way you can secure it against them making a separate copy. As you mention, any attempt at a licence key, or any other type of method, they’d be able to get around.
More Related Contents:
- How can I prevent SQL injection in PHP?
- SQL injection that gets around mysql_real_escape_string()
- Is “mysqli_real_escape_string” enough to avoid SQL injection or other SQL attacks?
- How to secure database passwords in PHP?
- Do htmlspecialchars and mysql_real_escape_string keep my PHP code safe from injection?
- How to encrypt/decrypt data in php?
- How do I use password hashing with PDO to make my code more secure? [closed]
- How to properly add cross-site request forgery (CSRF) token using PHP
- Examples of SQL Injections through addslashes()?
- PHP: Is mysql_real_escape_string sufficient for cleaning user input?
- preventing csrf in php
- PHP image upload security check list
- Generating cryptographically secure tokens
- How to best store user information and user login and password
- Many hash iterations: append salt every time?
- PHP: How To Disable Dangerous Functions
- Is it ever ok to store password in plain text in a php variable or php constant?
- How to prevent multiple logins in PHP website
- a better approach than storing mysql password in plain text in config file?
- What security issues should I look out for in PHP
- How do you set up use HttpOnly cookies in PHP
- Detecting Ajax in PHP and making sure request was from my own website
- What does mysql_real_escape_string() do that addslashes() doesn’t?
- Is it secure to store a password in a session? [duplicate]
- Use of Initialization Vector in openssl_encrypt
- What security problems could come from exposing phpinfo() to end users?
- Set httpOnly and secure on PHPSESSID cookie in PHP
- Json: PHP to JavaScript safe or not?
- Improve password hashing with a random salt
- Why is it considered bad practice to use “global” reference inside functions? [duplicate]