================================================= Maintenance for IBM Connect:Direct for UNIX 6.2.0 ================================================= This maintenance archive includes module replacements for the C:D UNIX 6.2.0 code base. It is applicable to C:D UNIX version 6.2.0, and contains all the new functionality and fixes as described in the C:D UNIX 6.2.0 Release notes, as well as fixes for the issues listed below. This release implements IBM's standard V.R.M.F method of identifying software. V, R, M and F are Version, Release, Modification and Fix Pack respectively. In general, V.R.M imply new functionality, while F is an accumulation of fixes called a Fix Pack. The term Fix Pack will be used going forward in place of Cumulative Maintenance. Individual fixes also have a new name, Interim Fixes, or iFixes for short. iFixes are numbered sequentially from one starting with any increment to V, R, M or F. Please see IBM's website for further details regarding this methodology. After applying the maintenance, the CLI banner will report that your C:D version is 6.2.0.x, where x is the current Fix Pack. It will also display the date that the maintenance was created. For more information, please refer to the C:D UNIX 6.2.0 Release Notes. ================================================= iFixes listed below apply to C:D for UNIX 6.2.0.0 ================================================= 001) CDUA-3012 commit date: 01 Sep 2021 ----------------------------------------- During a silent upgrade, initparm is updated to add the value of cdfa.enable same as that passed as option, if File Agent is installed inside CD Unix installation directory. So, cdfa.enable=y gets added even if standalone File Agent is installed. Updated code to add cdfa.enable=y only if Integrated File Agent is installed. 002) MFT-12365 / APAR IT37802 commit date: 14 Sep 2021 -------------------------------------------------------- C:D Install Agent startup creates a /tmp/.com_ibm_tools_attach directory used by the IBM Java Attach API. The IBM Java Attach API is not used in C:D, so the /tmp/.com_ibm_tools_attach directory creation is unnecessary and seen by some as a possible security risk. 003) MFT-12380 / APAR IT37900 commit date: 14 Sep 2021 -------------------------------------------------------- If the name of the S3 IO Exit is different of 'S3', the exception S3IOExitException: S3File: Invalid filename pathname is detected 'null' is raised. 004) CDUA-3013 commit date: 20 Sep 2021 ----------------------------------------- The CDWS connection is reset or logged out when apply changes button is clicked on file agent setting. The update of configuration fails for the integrated File Agent on ZLINUX server. The code is updated to handle the large configuration on ZLINUX. 005) CDUA-2889 commit date: 22 Sep 2021 ----------------------------------------- In the scenario where a user declines adding a local user, yet chooses to add a remote user, the remote user is added twice to the user file. The changes are done to prevent the creation of duplicate entries in the user file. 006) CDUA-2988 commit date: 27 Sep 2021 ----------------------------------------- Enabled user authority for stat logging from external sources like File Agent. If cmd.external.stat.log in userfile is set to 'n', File Agent won't be able to log its statistics in Connect Direct server's stats. 007) CDUA-2994 commit date: 28 Sep 2021 ----------------------------------------- A client request to view the initparm.cfg file may fail inappropriately with XCMM035I. 008) MFT-12352 / APAR IT38513 commit date: 29 Sep 2021 -------------------------------------------------------- Silent install of CD Unix fails intermittently due to failure in installation of Install Agent. When this issue occurs, a Java stack trace is produced that shows "java.lang.NullPointerException at com.zerog.ia.installer.LifeCycleManager.de". 009) CDUA-2043 / APAR IT37922 commit date: 05 Oct 2021 -------------------------------------------------------- A copy step using zFBA may fail and report message SCZF004E, Could not Open zFBA devices. If this failure is traced, the step may hang in execute state with a rapidly growing trace file output and ndmsmgr consuming significant CPU resource. 010) CDUA-2980 / APAR IT38016 commit date: 06 Oct 2021 -------------------------------------------------------- After upgrading to C:D Unix 6.0/6.1, an attempt to open the 'direct' prompt with a trace parameter failed with error XAPI005I Return Code: 8 Feedback: 0. Ensure that the ndmauth trace logs are always written to the ndm/bin directory to avoid permissions failures on creation of the trace logs. 011) MFT-11901 / APAR IT36440 commit date: 13 Oct 2021 -------------------------------------------------------- A process submit step (submit within a process) may fail and report an XPAE003I message if the submitted process text contains a comment on the first line. 012) MFT-12512 / APAR IT38545 commit date: 15 Oct 2021 -------------------------------------------------------- On some AIX systems, a submitted process will fail to execute, with statistics showing nothing more than a series of queue transitions from WAIT/WC to EXEC/PE to TIMER/WC, until retries are exhausted. 013) FLAG-256 commit date: 20 Oct 2021 ---------------------------------------- Integrated File Agent failed to connect to the Connect:Direct server with com.stercomm.csg.SPAdmin.JavaCDSP error in logs. Updated Integrated File Agent. 014) MFT-12318 / APAR IT37795 commit date: 20 Oct 2021 -------------------------------------------------------- Due to newer versions of Linux not maintaining binary compatibility for the Transport Independent RPC Library (libtirpc) with older versions, RHEL 8 and RHEL 7, for example, CDU binaries executed from a directory other than our ndm/bin directory may fail, indicating "error while loading shared libraries: libtirpc.so.1". See the Known Restrictions page of the CDU Release Notes for more details. The Known Restrictions page also describes a symbolic link which may be created to enable execution of CDU binaries from directories other than ndm/bin. If implementation of this link was desired, it had to be created manually. This fix updates the interactive and automated installation scripts to provide an option for creating this link during installs and upgrades. The interactive installation script, cdinstall, will prompt for the option if the link is not detected. A new parameter, cdai_tirpcCreateLink, has been added to the automated installation script, cdinstall_a, which takes a 'y' or 'n' value to optionally create this link. 015) CDUA-2983 commit date: 26 Oct 2021 ----------------------------------------- Integrated File Agent stats are not correctly displayed on Connect:Direct stats for some parameters. 016) FLAG-257 commit date: 27 Oct 2021 ----------------------------------------- Updated Integrated File Agent to Version 2.0.0.0_iFix007. ----------------------------------------------------------- iFixes listed above are accumulated in C:D for UNIX 6.2.0.1 ----------------------------------------------------------- =========================================================== iFixes listed below apply to C:D for UNIX 6.2.0.1 =========================================================== 001) CDUA-2946 commit date: 28 Oct 2021 ----------------------------------------- In the SCNT statistics record, the MSAS field, which reports the theoretical maximum number of simultaneous sessions a node could run (if licensed), is arbitrarily reporting 999, instead of calculating an appropriate value based on system resource limits. 002) MFT-12453 / APAR IT38835 commit date: 29 Oct 2021 -------------------------------------------------------- Building user exits with make_exit_c and make_exit_C may fail on later Linux versions, such as RHEL 8, indicating "fatal error: rpc/rpc.h: No such file or directory". 003) MFT-12582 / APAR IT38836 commit date: 03 Nov 2021 -------------------------------------------------------- S3 upload fails for 0 byte files when an aws policy denies non server side encrypted (sse) objects. 004) CDUA-3073 / APAR IT39028 commit date: 09 Nov 2021 -------------------------------------------------------- Various C:D UNIX executable modules, including cdpmgr, may fail to run on Ubuntu 20 systems, indicating an error loading shared library libtirpc.so.1. Note: With this iFix, Ubuntu versions 18 and 20 are added to the list of supported software for Intel and AMD x86-64. 005) MFT-12621 / APAR IT38901 commit date: 15 Nov 2021 -------------------------------------------------------- When an automated upgrade (cdinstall_a) fails due to Install Agent startup failure, the Install Agent logs describing the startup failure may be lost during the subsequent restore of the original CDU installed. Fix adds capturing the Install Agent logs and saving them in the deployment directory when this occurs. 006) CDUA-3085 commit date: 16 Nov 2021 ----------------------------------------- When a silent upgrade is performed from a CDU version where Install Agent is not up due to Secure+ not installed/configured, upgrade is marked as failed as Install Agent is unable to start even after upgrade. As a part of this fix, Install Agent startup is not attempted after a silent upgrade, if it was not up before upgrade. 007) CDUA-2754 commit date: 16 Nov 2021 -------------------------------------------------------- The SSLV2 hello has been disabled. Note that TLS 1.0 is deprecated by the IETF since March 2021. 008) CDUA-3064 commit date: 17 Nov 2021 ----------------------------------------- Sometimes deployment fails during container/helm chart upgrade and configuration present on persistent volume is also lost. Now, when new container/pod comes up it doesn't have previous configuration. 009) CDUA-3106 commit date: 29 Nov 2021 ----------------------------------------- User Id is not captured in stats when a user sign on to CDU server fails. 010) CDUA-3096 commit date: 02 Dec 2021 ----------------------------------------- When changes to initparm.cfg is done using CDWS or CCM and pod is deleted so that new pod comes up with updated initparm.cfg parameters. But new pod fails to come up and keeps on restaring showing error CD service not started. 011) CDUA-2830 / APAR IT39113 commit date: 03 Dec 2021 -------------------------------------------------------- If the connection is broken when CDU is pnode pulling a file from a remote node to an S3 destination with checkpoint enabled, on restart, the checkpoint resynchronization fails with error message FIOX023E reported, and the copy step is restarted from the beginning. 012) CDUA-3134 / APAR IT39167 commit date: 02 Dec 2021 -------------------------------------------------------- Expired passwords are not detected by CDU when authenticating credentials on HP-UX Itanium and AIX platforms. Also, when credential validation failed, no reason was logged for the failure. Fix adds a new message, XIDC001I, logged only on the validating side and viewable only by administrators, indicating why credential validation was failed. 013) CDUA-3056 commit date: 06 Dec 2021 ---------------------------------------- In some scenarios, C:D Control Center may incorrectly conclude that multiple C:D UNIX nodes are running on the same system. 014) MFT-11969 / APAR IT36604 commit date: 07 Dec 2021 -------------------------------------------------------- When a remote C:D initiates a secure session to C:D UNIX (CDU) requesting Secure+ protocols that are not supported by CDU, and CDU has Secure+ Override enabled for that incoming session, it's possible that the session will fail inappropriately with a CSPA091E message. 015) CDUA-2698 commit date: 07 Dec 2021 ----------------------------------------- SPCli shows a Basename parameter when displaying a remote node, which is inappropriate since the Basename parameter became irrelevant when the Secure+ STS protocol was dropped from support. 016) MFT-12769 / APAR IT39369 commit date: 12 Dec 2021 -------------------------------------------------------- The S3 File IO Exit, Install Agent, and File Agent components, included in IBM Sterling Connect:Direct for UNIX use versions of Apache Log4j2 that are vulnerable to the below listed issue. Apache Log4j2 has been upgraded to version 2.15.0. CVE-2021-44228: JNDI features of Apache Log4j2 versions <= 2.14.1, used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. 017) MFT-12790 / APAR IT39452 commit date: 17 Dec 2021 -------------------------------------------------------- The S3 File IO Exit, Install Agent, and File Agent components, included in IBM Sterling Connect:Direct for UNIX use versions of Apache Log4j2 that are vulnerable to the below listed issue. Apache log4j2 has been upgraded to version 2.16.0. CVE-2021-45046: Apache Log4j is vulnerable to a denial of service, caused by an incomplete fix of CVE-2021-44228 in certain non-default configurations. A remote attacker with control over Thread Context Map (MDC) input data or a Thread Context Map pattern to exploit this vulnerability to craft malicious input data using a JNDI Lookup pattern and cause a denial of service. 018) MFT-12807 / APAR IT39480 commit date: 21 Dec 2021 ------------------------------------------------------- The S3 File IO Exit, Install Agent, and File Agent components, included in IBM Sterling Connect:Direct for UNIX use versions of Apache Log4j2 that are vulnerable to the below listed issue. Apache log4j2 has been upgraded to version 2.17.0. CVE-2021-45105: Apache Log4j versions <= 2.16.0 did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted.