[2.0.104] FSE-Windows - December 24, 2024

1. Overview

This article provides an overview of new features and known issues in the Fortanix Filesystem Encryption (FSE)-Windows 2.0.104 release. 

2. New Features

• The Fortanix FSE Agent can now operate as a Windows service for smoother operations (JIRA: FSE-99).
  For more information, refer to the following:

  • Filesystem Encryption for Windows as a Service Using Fortanix Data Security Manager - Setup and Usage

  • Filesystem Encryption for Windows as a Service - Concepts

• The Filesystem Encryption Agent now supports Key Encryption Key (KEK) rotation with seamless Data Encryption Keys (DEKs) re-encryption, ensuring zero downtime for encrypted file system operations (JIRA: FSE-108).
  For more information, refer to Filesystem Encryption for Windows as a Service Using Fortanix Data Security Manager - Client Configuration.

3. Bug Fixes

• 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 the 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.

4. Installation