Linux Patch Notes for CTE v7.6.0

Patch Information
Release	v7.6.0.134
Date	2024-11-13
Document version	2

Enhancements

• CipherTrust Data Security Platform Services

  This patch adds support for CipherTrust Data Security Platform Services (CDSPaaS) as a key manager.

Limitation

• Teradata Deployments

  This patch is not supported for Teradata deployments running SLES 12 SP3.

Resolved Issues

• AGT-57666 [CS1545309]: Unable to create a symlink with a policy that allows an f_link action

  The issue occurred when a policy with f_link,f_rd_att,f_chg_att,f_rd_sec permissions should have allowed creation of a symbolic link, inside of a GuardPoint, to a target file, also in the same GuardPoint. However, users were getting permission denied error because CTE could not determine that the symlink being created was the proper file type. The solution was to fix the code to accurately determine the object type for the symlink.

• AGT-59842: [CS1554471] High Memory Consumption by VMD process

  In the code that formats log messages prior to uploading them to CipherTrust Manager, an array of variables was allocated to contain formatted strings, but the strings were not freed on completion. The memory leak was small for each message, but with a high volume of logging from CipherTrust Transparent Encryption to CipherTrust Manager, the memory leaks built up over time. The solution was to fix the memory leaks.

• AGT-60987 [CS1571917]: CTE 7.6.0.114 fails on SLES 15 SP5 with no suitable module found kernel error

  The issue was the presence of the /etc/SuSE-release file, which pointed to the an incorrect distribution. The solution was to delete the file.

• AGT-61385: Getting unnecessary logs while installing agent on RHEL 8.10 and RHEL 8

  The errors were created due to the parsing of, and comparison to, fields in different kernel versions with RHEL 8.10, to validate compatibility. The scenarios originated post RHEL 8.10 kernel support because it contains fields of different lengths compared to other RHEL 8 versions. The solution was to make code changes to manage the case with RHEL 8.10 kernels to eliminate the errors.

Known Issues

No Known Issues at this time.