The tab "Additional options" offers the following additional protection options.
Password
This data object defines an application password, which will be required every time the application is launched. This feature can be useful as a "nag screen" when making demo versions or for additional security.
Application Checksum
This data object defines a checksum, calculated for the protected application file. Its value will be stored in the CRYPTO-BOX and used to check if the application was manipulated or corrupted, as well as prevent unauthorized modification. The checksum cannot be set by value, it is calculated only after successful application protection.
Application Name Hash
This data object is specific to AutoCrypt projects: it contains a hash value calculated for the name of protected application. This hash value will be stored in the CRYPTO-BOX and used to check if the application was renamed on the user side. The application name hash can’t be set by value, it is calculated after successful application protection.
Signature (GUID)
This option is mainly for software developers:
It allows you to store an individual data block (up to 16 bytes length) in the CRYPTO-BOX memory (e.g. customer specific data) and provide it directly to your protected application – with minimal efforts!
The advantage of this approach: there is no knowledge about the CRYPTO-BOX API necessary – just copy the code snippet from our sample application source code to your application source code.
After license validation was successful, AutoCrypt will read the data from the CRYPTO-BOX, decrypts it and writes it to a buffer signed with a unique signature which can be identified and read by your application.
A readme file with detailed instructions and sample code can be found in the Protection Kit:
[Smarx PPK root folder]\SmarxOS\API\Win\Samples\ReadMemoryBySignature
Application Checksum and Application Name Hash cannot be used if the application partition is shared between two or more applications (see also Adding Applications to the Project). Furthermore, it is not recommended to use these options if you plan to update your application regularly, because the new application will not be compatible with existing Checksum/Hash settings stored in the CRYPTO-BOX.