Decrypt Verifiers check rules to determine if a decrypt is allowed.

1. Decrypt Verifiers check rules to determine if a decrypt is allowed. Though encryption of the assembly by itself stops decompiler applications from easily stripping your code from the file. Decrypt Verifiers go further by attempting to block when a decrypt can occur at all. This can include things such as checking the properties of the calling process to see if it is the application you are expecting to be asking for a decrypt. Or you could also require that the contents of a text file match an exact string. Verifiers are not necessarily mutually exclusive, so you can use more than one at the same time. The built-in News Flash feature will let you know when new types of Decrypt Verifiers are available.

2. Verify local text file • This type of verifier allows you to provide a path relative to the process exe which points to a text file. This text file contains a string you want to match. If the file is not present or the contents of the file do not match your string then the decrypt will not occur. The string you enter is scrambled and embedded inside the unmanaged C++ lock core to make it more difficult for someone to figure how and what you are doing.

3. Verify calling process properties • This verifier looks at the process exe that is calling into the AssemblyLockbox and checks for properties that you specify. The screen shot below shows the properties that you can check at this time. The properties on the right are in AssemblyLockboxBuilder and the picture on the left shows the properties of an exe file. If these properties are set to values that don’t match your exe then the decrypt will not occur.