Application signature uniquely identifies project files and thus protected application on remote computer. Applications protected with same application signature will share the same license information on remote computers.
It can be any string value with minimal length of 6 and maximal length of 10 characters.
For example, if you have application named "Text editor PRO V4.0" your application signature could be "TEEDPROV40".
Application signature is highly important!
- It enables installation of application updates without entering new (or original) activation code again (both original application and update should share the same application signature).
- It enables sharing of license information between a group of applications. For example, a group of applications can be activated with single activation code (all applications should share the same application signature in this case).
- Machine ID (MID) code is also based on application signature. In this way activation codes can be generated for applications protected with appropriate project only. If wrong project is loaded MID code decryption error will be reported.
- Do not change Program ID value (encryption key) for program update without changing Application signature (see "File damaged! error message").
- Two (or more) applications protected with same Application signature, Program ID and same locking parameters will generate same Site/MID code.
- If you are distributing free updates for your application use the same project settings (including Application signature) as for original application. New update will be automatically unlocked in such cases.
- If your are distributing non-free updates for your application you should change Application signature and new update will generate different Site/MID code. You can also consider using different Program ID for such updates.
- Be sure to use the same ProgramID for applications with same Application signature. If you have two applications with same application signature and different Program ID running on same computer one of them will be wrongly decrypted and will display "File damaged!" warning message. Both applications will share same license data including Program ID (encryption key) and this is why one of them will be wrongly decrypted.
- In order to test different protection scenarios you need to use different application signature for each strategy in order to avoid possible conflicts when experimenting with different project settings. You can use special application signature values for each test build like TEST0001, TEST0002, TEST0003 and so on.