1. Overview
This article provides an overview of new features and resolved issues in the Fortanix Filesystem Encryption (FSE)-Windows 2.4.182 release.
2. New Features
Added support for configurable logging preferences at the Fortanix FSE agent level on Windows (JIRA: FSE-457).
For more information, refer to Filesystem Encryption for Windows as a Service Using Fortanix Data Security Manager - Client Configuration.
3. Bug Fixes
Fixed an issue where service failure did not generate crash reports in the service-based architecture (JIRA: FSE-459).
4. Known Issues
If the Fortanix FSE Agent 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 an 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.
5. Installation
To install the latest Filesystem Encryption package for Windows, click here.