[2.1.109] FSE-Windows - February 20, 2025

1. Overview

This article provides an overview of new features, improvements, and bug fixes in the Fortanix Filesystem Encryption (FSE)-Windows 2.1.109 release.

Added Skip Certificate Validation toggle to the SETTINGS tab in the Windows Fortanix Encryption Agent, allowing users to bypass the certificate validation check (JIRA: FSE-343).
For more information, refer to Filesystem Encryption for Windows as a Service Using Fortanix Data Security Manager - Client Configuration.

Added meta details to the security object for hostname and cipherdir (JIRA: FSE-348).
Updated the refresh button ( ) position from the FILE SYSTEM tab to the Fortanix File System Encryption Agent home/starting page for improved accessibility and consistency across the user interface (UI) (JIRA: FSE-300).

Fixed an issue where FSE agent initialization failed with the SSL error: "Check revocation status failed," occurring when using a Fortanix DSM server with a certificate lacking Certificate Revocation List (CRL) information or when the CRL endpoint was unreachable (JIRA: FSE-342).
Fixed an issue where the FSE Agent failed to initialize and mount a network drive mapped to a local system drive (JIRA: FSE-335).
Fixed an issue where LookupAccountName failed immediately after the creation of a local group (JIRA: FSE-333).
Fixed the following UI issues on the Initialize Filesystem page (JIRA: FSE-312):
- Resolved an issue where the Optional details dropdown was not visible in the default modal size, requiring users to scroll down to access the optional parameters in the dropdown.
- Fixed the display of the Long name max field when File Name Encryption was set to Plain Text.
- Added a checkmark to the check boxes for improved clarity.
- Fixed the issue where Long name max field was displayed as a string instead of a number.

If the Fortanix FSE Agent user interface (UI) is already running in an admin login session, it might not open or may freeze when attempting to launch it as an admin in another user's login session (JIRA: FSE-321).
Workaround: To prevent the UI from freezing or failing to open, launch it only once per user at a time or only once as admin across all user sessions.
The Fortanix FSE agent does not restrict access to files such as databases and logs by default. This means that unauthorized users might access them (JIRA: FSE-185).
Workaround: Set file permissions to ensure only the Fortanix FSE Agent’s service account and authorized administrators can access these files.
Named pipe squatting occurs when an unauthorized process listens on a named pipe before the Fortanix Filesystem Encryption service starts. This may lead users to mistakenly connect to the unauthorized process instead of the legitimate service (JIRA: FSE-161).
Workaround: Ensure that no other service or application on the server uses the same named pipe as the Fortanix Filesystem Encryption service.

To install the latest Filesystem Encryption package for Windows, click here.