[4.34] Patch 2 - March 17, 2025

Fortanix Data Security Manager (DSM) 4.34.2545 release provides an overview of improvements and known issues.

This release is superseded by the June 24, 2025, release.

WARNING

• You are REQUIRED to upgrade Fortanix DSM to version 4.27 or 4.31 before upgrading to version 4.34.2545. If you want to upgrade Fortanix DSM to version 4.34.2545 from a version earlier than 4.27, please contact the Fortanix Support team at your earliest to validate the upgrade path.

• Downgrade from 4.34.2545 to any prior version is not supported due to the DCAP migration.

• You may observe delay (retries) in bringing up services post upgrade to DSM 4.34.2545 due to a new table creation in the database to support the new Key Expiry Alert feature. For more details, contact Fortanix Support.

• For 1-node cluster, the upgrade path must be 4.27 to 4.31 and 4.31 to 4.34.2545.

• For 3-node clusters, the upgrade path must be 4.27 to 4.34.2545.

NOTE

• This release is specifically for customers who have an attestation-level proxy configured and do not want to switch to the global proxy.

• The Fortanix DSM cluster upgrade must be done with Fortanix Support on call. Please reach out to Fortanix support if you are planning an upgrade.

• The customer's BIOS version must be checked by Fortanix Support before the Fortanix DSM software upgrade. If required, the BIOS version should be upgraded to the latest version and verified by Fortanix Support for a smooth upgrade.

• If your Fortanix DSM version is 4.31 or later, then the HSM Gateway version must also be 4.31 or later. Similarly, if the HSM Gateway version is 4.31 or later, then your Fortanix DSM version must be 4.31 or later.

1. Improvements

• Added proxy support for Data Center Attestation Primitives (DCAP) attestation and ensure that the DCAP and Intel Attestation Service (IAS) proxy settings only affect the attestation network flow (JIRA: DEVOPS-5569).
  For more information, refer to Fortanix DSM Installation Guide. 

2. Known Issues

• kube-apiserver IP inconsistency persists when different peer IPs are used for joining node (JIRA: DEVOPS-5040).
  Workaround: Contact Fortanix Support for a workaround.

For a complete list of new features, enhancements to existing features, other improvements, bug fixes, and known issues, refer to the full description of the DSM 4.34 release notes.