Background details
- With FRP 5.0.6 and earlier, it was possible to configure the FRP encryption policy settings for applications based on their process names. Changes were made from the Application-based Protection policy page.
- With FRP 5.0.7 and later, policy configuration is simplified by allowing administrators some flexibility around the process and extension names.
In
FRP 5.0.6 and earlier this simplification is achieved by the following process:
- Click Add/+. This action specifies the process and the file extensions to be encrypted.
- To encrypt files created by the application, specify the process name of the application as seen in the Windows Process Explorer. For example, notepad.exe and test.exe.
- Specify the file extensions to be encrypted without a period (.) that the process supports. For example, txt and doc. Multiple file extensions can be specified using a space, semicolon, or colon as separators.
- Specify the encryption key to be assigned to the policy. Browse to select the needed key.
With
FRP 5.0.7 and later versions this simplification is achieved by:
- Click Add/+. This action specifies the process and the file extensions to be encrypted.
- Specify the process name of the application:
- Option 1 - Specify the process name as seen in the Windows Process Explorer to encrypt files created by the application. For example, notepad.exe and test.exe.
- Option 2 - Specify the process name without a suffix (such as .exe and.com). For example, notepad and test.
- Specify the file extensions to be encrypted. For example, txt, doc, xls, and tmp that the process supports. Multiple file extensions can be specified using a space, semicolon, or colon as separators.
- Specify the encryption key to be assigned to the policy. Browse to select the key.
NOTES:
- The above changes do not affect any existing policies.
- Administrators can continue to configure their policy settings as they do in earlier FRP versions. Or, they can start to configure the policy settings according to the above FRP 5.0.7 changes. This change does not affect the client function.
