creating license file for code deployment

Hello,

I am developing Matlab codes that I will be giving to people in protected form either p.code or executable. My concern is how to create an activation file (a license key for this code). That check the time left, the computer that the code is running. Is there a way of doing that in MATLAB or I need to use a 3rd party solution?

Thank you

Answer 1

[Walter Roberson]

MATLAB (and Mathworks) do not offer any facility for that. You can build your own solution or you can use a third-party solution.

[Kamuran]

Any suggestion for 3rd party solution because I have no experience on creating such protection.

[Walter Roberson]

Mathworks and many other manufacturers use FlexLM, but it might be more complicated than you need or more expensive.

I do not have experience with other vendors. There are quite a number available; see for example https://www.google.com/search?q=license+protection+software

Answer 2

[Jan]

There cannot be a 100% reliable method to restrict the usage of your code. Remember that you can run P-functions in the debugger and examine the results of each line of code. The user has the full control over all toolbox functions of Matlab, such that e.g. comparing passwords by strcmp can be manipulated with 4 lines of trivial code.

Checking the time and the computer can be broken easily by running the code in a virtual machine.

You find many instructions for bypassing the copy protection of any commercial software I know. The higher the protection level, the lower is the usability for the customer - and this increases the demand to circumvent the protection even for users, who have payed for the software.

So my conclusion is, that the costs (counted in $ and hours of work) of the copy-protection should be related to the estimated costs caused by illegal usage of the software. In my case the best (in terms of solidity) protection is a printed license agreement, which must be signed by hand and sent back. The license agreements and NDAs, which are accepted by clicking on any checkboxes, are neither read nor considered by users.

@Mathworks: The value of P-coding is low, as long as the P-functions can be processed in the debugger. I cannot see any constructive need for debugging P-files. So why is this feature still supported?