Licence Protector uses standard encryption methods in combination with a personal encryption. As personal encryption the

 

 

is used. For decryption, the ReadKey is used. See chapter Project Keys how to generate these keys. If you are using the Basic Security Level (not recommended), then only the Project Secure Key is used for encryption and decryption.

 

The Professional Edition allows to use a password protected ReadKey/WriteKey - see Additional protection.

 

If a hacker would steel the ReadKey (which is used in the application), he would not be able to make a generator to produce license files or Activation Keys. This would require also the WriteKey and Project Secure Key. See also how to Hide the Read Key in your source code.

 

Security Considerations

As all keys are inside the license file template, you improve security using these steps.

 

After finishing the integration, generate new Project Keys. Now distribute the template as follows:

 

Development

Make a project template, which includes only the ReadKey. This project template can be used by development. The source code requires only the ReadKey in the PrepareAndCheck, Prepare or PrepareAdvanced statement.

 

Administration

The License Generator needs a project template with WriteKey and Project Secure Key. If an existing license file should be opened within the License Generator, then the ReadKey is necessary.

 

Depending on your needs you can make a project template which includes only:

 

 

You could also make a Web Based interface to generate the keys using the Automatic License Generator. This allows to place the project template on a server and limit the file access.

 

With the Professional Edition, use only the ProtectedRead and ProtectedWrite Key.

Activation Server

The Activation Server needs a project template with ReadKey, WriteKey and Project Secure Key.

 

Automatic License Generator

Depending on your needs you can make a project template which includes only:

 

 

A ReadKey is not necessary.