Licence Protector 5

Navigation: Implementing Licence Protector using default workflow > Project Template - define license file

Project Keys / Personal Encryption

Each project has an own encryption to ensure, that keys and license files are unique.

The personalization is achieved with a Read Key (used in the application to read/open license files = decryption) and a Write Key (in the Generator to create files = encryption). For certain encryption issues a Project Secure Key is used. See chapter SecurityLevel for background information.

This ensures that:

•a hacker can never build a generator as he would need all 3 encryption keys (Read Key, Write Key, Project Secure Key)

•every product has a different encryption so that a Serial Number for product A would never work for product B

After finishing all tests, the demo keys in the project template have to be replaced with encryption keys, which are unique for the project. Use TAB File, Copy Project to get new encryption keys for an existing template or TAB File, Create Project to create a new template with new encryption keys..