================================================================================== Copyright © Aricent Holdings Luxembourg S.a.r.l. 2018, 2019. All rights reserved. ================================================================================== ========================================================== Maintenance for IBM Sterling Connect:Direct for UNIX 4.3.0 ========================================================== This maintenance archive includes module replacements for the C:D UNIX 4.3.0 code base. It is applicable to C:D UNIX version 4.3.0, and contains all the new functionality and fixes as described in the C:D UNIX 4.3.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 4.3.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 4.3.0 Release Notes. ================================================= iFixes listed below apply to C:D for UNIX 4.3.0.0 ================================================= 001) RTC523522 / APAR IT18957 commit date: 26 Apr 2018 -------------------------------------------------------- In rare circumstances, a text file sent to a destination file with fixed block record format on z/OS may be padded with ASCII blanks instead of EBCDIC. 002) RTC552947 / APAR IT24014 commit date: 30 Apr 2018 -------------------------------------------------------- When Secure+ security mode is disabled, session establishment can be expected to take less time than when a security mode, FIPS 140-2, for example, is enabled. However, session establishment with security mode disabled takes the same amount of time as when enabled. Session establishment times may also be increased if cdpmgr inherits a large maximum file descriptor system resource limit. 003) RTC564598 / APAR IT25140 commit date: 24 May 2018 -------------------------------------------------------- Incoming Secure+ session incorrectly allowed when the .Local node has Secure+ enabled and there is no Secure+ entry for the remote node. 004) RTC561582 / APAR IT24339 commit date: 25 May 2018 -------------------------------------------------------- Copy send performance to C:D Z/OS can be degraded when the UNIX source file sysopts includes "datatype=binary", and the Z/OS destination file record format is VB or FB. 005) RTC561515 commit date: 22 June 2018 ------------------------------------------ When alt.comm.outbound is configured on a remote node, traverse the alt.comm.outbound list on each process retry until we have a successful connection to the remote node. 006) RTC568699 commit date: 05 July 2018 ------------------------------------------ Customization fails with a syntax error during installation of C:D UNIX 4.3 on Solaris. 007) MFT-9886 commit date: 15 Aug 2018 ---------------------------------------- Connect:Direct for UNIX Secure+ uses IBM Java Runtime, which is vulnerable to the following issue: CVE-2018-2602: An unspecified vulnerability related to the Java SE I18n component could allow an unauthenticated attacker to cause low confidentiality impact, low integrity impact, and low availability impact. 008) MFT-9824 commit date: 16 Aug 2018 ---------------------------------------- A process may terminate abruptly with statistics reporting "SMGR terminated by signal". A known manifestation of this issue is likely to occur when a run job on a C:D z/OS node is attempted. 009) RTC562386 / APAR IT24362 commit date: 04 Sep 2018 -------------------------------------------------------- Parser error XPAE003I may be generated when submitting a process that has an snodeid coded with a 'Y' or 'N' character for the password. 010) RTC565352 / APAR IT24904 commit date: 04 Sep 2018 -------------------------------------------------------- There are three possible issues that may occur when sending a text file a to a z/OS destination that uses VB format with LRECL=BLKSIZE+4: . If the first record is within four bytes of the block size, the transfer will fail with an SVSJ045I message. . If the first record is four bytes or more smaller than the block size, and a subsequent record fills an entire block exactly, the z/OS destination file will be corrupted. . If the first record is four bytes or more smaller than the block size, and a subsequent record is up to four bytes longer than the maximum record size, this error condition will not be detected, and the z/OS destination file will be corrupted. 011) RTC567101 / APAR IT24905 commit date: 04 Sep 2018 -------------------------------------------------------- When sending a file to C:D z/OS and specifying the SYSOUT SYSOPTS parameter, CDU may inappropriately set the destination record format (RECFM) to VB. 012) RTC564088 / APAR IT25329 commit date: 04 Sep 2018 -------------------------------------------------------- Writes to stdout within a run job or run task may be reflected in C:D UNIX traces, even after traces are turned off. 013) RTC565959 commit date: 04 Sep 2018 ----------------------------------------- In some circumstances, an attempt to update the .Local node record via the Secure+ Admin Tool will fail reporting something similar to "Error #6 - Remote Node file not found." 014) RTC566602 / MFT-9446 / APAR IT26480 commit date: 04 Sep 2018 ------------------------------------------------------------------- On AIX systems, C:D UNIX executables will inappropriately prefer run time libraries in /usr/vac/lib and /usr/vacpp/lib directories instead of the standard /usr/lib /lib directories. The /usr/vac/lib and /usr/vacpp/lib directories may be populated if an IBM compiler is installed on the system, for example. If the libraries in /usr/vac/lib and /usr/vacpp/lib are old or otherwise incompatible with the C:D UNIX executables, various errors may occur, including XSMG609I, SMGR (pnode) failed to convert FMH68 to network format. 015) RTC571051 / MFT-9588 / APAR IT26481 commit date: 04 Sep 2018 ------------------------------------------------------------------- In rare circumstances, a process may fail to start, reporting an XSCM006E error, all users are denied access to CD from the SACL, even though the Strong Access Control (SACL) directory and file appear to have correct ownership and permissions set. Enhanced error messages to provide greater detail when this happens. 016) MFT-9613 / APAR IT26158 commit date: 10 Sep 2018 ------------------------------------------------------- The Connect:Direct for Unix UI will fail when opening ndmapi.cfg if the local file system has assigned to the file an inode number greater than 32 bits in size. 017) CDUA-1102 commit date: 16 Aug 2018 ----------------------------------------- An update proxy command issued from a KQV client, such as C:D Browser or IBM Control Center, may fail indicating "The variable proxy name was out of bounds", even though the proxy name is valid. 018) MFT-10001 / APAR IT26905 commit date: 14 Nov 2018 -------------------------------------------------------- IBM Sterling Connect:Direct for UNIX uses IBM Runtime Environment Java. (JRE) Versions 8.0.5.15 and 7.0.10.25. These JREs are vulnerable to the following issues, disclosed as part of the IBM Java SDK updates in July 2018: CVE-2018-12539: Eclipse OpenJ9 could allow a local attacker to gain elevated privileges on the system, caused by the failure to restrict the use of Java Attach API to connect to an Eclipse OpenJ9 or IBM JVM on the same machine and use Attach API operations to only the process owner. An attacker could exploit this vulnerability to execute untrusted native code and gain elevated privileges on the system. CVE-2018-1656: The IBM Java Runtime Environment's Diagnostic Tooling Framework for Java (DTFJ) does not protect against path traversal attacks when extracting compressed dump files. 019) MFT-9969 / APAR IT27224 commit date: 07 Dec 2018 ------------------------------------------------------- Using the Amazon S3 file IO exit to receive a zero byte file fails, reporting message FIOX044E. 020) MFT-9996 / APAR IT27673 commit date: 09 Jan 2019 ------------------------------------------------------ A backup created when running the interactive script may incur permission errors when writing to the installation directory's parent folder. Instead, create the backup in the installation directory. 021) MFT-10047 / APAR IT27442 commit date: 10 Jan 2019 -------------------------------------------------------- When upgrading a C:D UNIX node with an existing keystore, a keystore password is not required. However, the automated install script, cdinstall_a, fails reporting CDAI003E when the cdai_installCmd is set to "upgrade" and no cdai_keystorePassword parameter is coded. 022) MFT-9526 / APAR IT26469 commit date: 14 Jan 2019 ------------------------------------------------------- To run C:D UNIX on Solaris 10 requires Update 10 or greater. Updates may be applied as a full release or as a patchset. cdinstall correctly recognizes a full release Update, but wasn't recognizing a patchset update and failed the install. 023) MFT-10026 / APAR IT27933 commit date: 30 Jan 2019 -------------------------------------------------------- After installing or upgrading to C:D UNIX 4.3.0.0.iFix018, the banners of the Secure+ administration tools, SPAdmin and SPCli, refer to C:D UNIX 4.2.0.4. 024) MFT-9523 / APAR IT26470 commit date: 04 Feb 2019 ------------------------------------------------------- Control Center not reading CDU Secure+ presence correctly. 025) MFT-10143 / APAR IT28061 commit date: 12Feb 2019 ------------------------------------------------------- A proxy update issued by a KQV client does not complete successfully if the user name or node name contains a period. 026) MFT-9917 / APAR IT27019 commit date: 13 Feb 2019 ------------------------------------------------------- An ICC select process command submitted to C:D UNIX may occasionally fail with CNCD058E message. 027) MFT-9967 / APAR IT26865 commit date: 07 Mar 2019 ------------------------------------------------------- CD UNIX may allow a user with sudo access restricted to certain CD UNIX executable files to expand access beyond the restriction, as indicated in the following issue: CVE-2018-1903: IBM Sterling Connect:Direct for UNIX could allow a user with restricted sudo access on a system to manipulate CD UNIX to gain full sudo access. 028) MFT-10116 / APAR IT27777 commit date: 20 Mar 2019 -------------------------------------------------------- A COPY to the local destination file /dev/null fails with error XSQF006I, feedback code 22. 029) MFT-10016 / APAR IT28408 commit date: 25 mar 2019 ------------------------------------------------------- Transfer rate to AWS S3 needs improvement. This fix also adds support for direct access to S3 from an on-premises node The following new properties are available and can be used in initparm.cfg file or sysopts: s3.endPointUrl IP or hostname to access S3 services. Amazon S3 endpoint is the default. Example: s3.endpointUrl=my.s3provider.com s3.endPointPort Port to use if any. No default value. Example: s3.endpointPort=8080 s3.endPointSecure Secure or non secure access. HTTPS or HTTP requests. YES is the default. Example: s3.endpointSecure=NO s3.profilePath Credential file to use. Amazon credentials search order is the default. Example: s3.profilePath='/opt/some path/credentials' s3.profileName Profile name to use from credential file. default is the amazon S3 default [default] Example: s3.profileName=otherprofile s3.executorQueue Parallel transfer upload queue size. Default is 5. s3.executorMinPool Parallel upload. Initial number of transfer upload threads to use. Default is 10. s3.executorMaxPool Parallel upload. Maximum number of transfer upload threads to use. Default is 30. Max value is AmazonS3 max connections (50).