Best way to secure source code

#1

I use wappler to extend a web application that’s hosted on my clients server.

They have a Windows Server with IIS and MS SQL Server.
My Wappler created pages are currently hosted on this same machine.

What is the easiest way to prevent the wwwroot folder of my site being copied and used elsewhere with a slight modification to the database connection parameters in dmxConnect\modules\Connections

Would just copying the .asp pages in dmxConnect\api and hosting on my own server and remove them from the customer machine, modify the paths work?

I would like to have the absolute minimum files on my customers office server.

Many thanks in advance

1 Like
#2

Any suggestions would be really appreciated.

#3

I guess, in theory, if the customers MS Sql server would accept connections from your server you could host the fields remotely either via a separate URL or inside iframes but it is not going to be a seamless solution. Difficult to be specific with the limited information you have given

#4

If somebody has direct root access to the host they could easily copy the entire directory (or if the host is poorly configured and insecure). Likewise if they have backups running, they could restore your directory to another location. In these circumstances there would be little you could do to stop such activity. The best option would be to host your own application and put yourself in charge of access to the files associated with it. Then allow your Client access via strict privileges for example (white-listed I.Ps only etc).

#5

early years I was using Ioncube. Not sure if it still exists. It secured your code.